Guild Wars 2

Puandro.3245:

Jaxxeh.8614:

Will they still bind on acquire, however? Because that’s really the issue here I believe ^^

My guess is when they fix it, it will fix the new ones also.

My point is, some of the exotics right now are bind on acquire instead of bind on use/equip, which was the issue raised by the OP. That they will be merely account bound instead of soul bound (William’s reply) is a secondary concern. I just hope they fix the binding mechanic.

Will they still bind on acquire, however? Because that’s really the issue here I believe ^^

Having condition removal helps a lot. Other than that, it’s just a matter of coordination & teamwork, and a bit of luck.

It’s a bug. Read this post :
https://forum-en.gw2archive.eu/forum/game/dungeons/New-dungeon-exotic-bind-on-pick-up/765310

Seeing the Colossus turning around and giving us the “Namaste” nod after we’d freed him made my day. And the other fractals we ran were entertaining/challenging/fun as well (Champion Rabbit lol). Kudos & thanks!

This is pointless and dumb, an abject failure. Unplayable.

Hi Paul,

Thank you for taking the time to explain the probable cause of the issue and how it affects the diagnostic & repair process. Now I understand, and it makes perfect sense.

Not sure if my problem was actual faulty RAM or Virtual Memory issues (like a bad sector on the drive where Virtual Memory is located). I’ve freed additional space and moved the game to another drive and haven’t had an error since. However, RAM or drive, it’s most definitely a hardware issue, and your suggestion to address it if & when evidence is found is sound advice. Thank you again.

I have the same issue. What I really don’t understand is, if it’s a memory issue (my first thought as well), then why is the game forcing you to do a complete archive check & repair? Memory != File System.

I can live with the occasional crash, it’s the lengthy repair process that’s killing me.