Guild Wars 2

You’re complaining because they fixed a bug?

tolunart.2095:

You’re complaining because they fixed a bug?

its more of a workaround than an actual fix.
especially if you used to transmute your items before and never heard of the fix.
i was really confused when suddenly i couldn’t transmute my items anymore and i didn’t get an error message or anything. it simply didnt do anything.

Yes, it’s a workaround. With DR not working as intended and causing massive kittenfests across several different kinds of content, they may not have the time to chase down a rare and non-game-breaking bug. So they initiated a workaround to stop it from happening while they fixed the important stuff.

OP’s statement is essentially “how dare you slightly inconvenience me so that you can work on problems that are causing massive and highly visible protests and chasing away your customers!”

At best, it’s an annoying example of player entitlement attitude. Just because he did not encounter the bug doesn’t mean that it doesn’t exist or shouldn’t be dealt with. If OP wants to determine how they deal with the bug, he can go to college, get degrees in relevant computer programming and graphic design fields, go to work for Arenanet, be promoted and get put in charge of fixing bugs. Then he can tell people what to do about the naked bug.

FYI, if you don’t dequip it consumes a stone even though it doesn’t work and there is no error message. I lost 3-4 stones that way.

Ummm read the patch notes? There was a link right there in your game client when you launched it.

Y’know, I feel kinda dumb now, ‘cause all this time I have been taking off items before transmuting them as I figured you couldn’t transmute items while they were being worn. ^^; I’d always just switch to town clothes while I was transmuting so my character wouldn’t have to stand around in his/her undies.

I imagine the change could be confusing though if you were used to transmuting items you were wearing! And that is really awful about lost transmutation stones.

What WAS the bug that this change was supposed to workaround, anyway?