Guild Wars 2

So, Shadow Shot lists itself as an “Unblockable” skill, yet I’ve encountered numerous instances in PvP as of late where a guardian blocks it 2 or 3 times in a row like it’s no big deal. Thus, I don’t know if it’s not truly unblockable, and if that’s the case, then please take the label off of the skill, but if it is intended to be completely unblockable, then make it unblockable, against rangers, warriors, guards, etc. Please and thank you.

After the last update, my client seems to be having an issue. Every time I rapidly click on bags to open multiple at a time, or any time there is intense activity during gameplay, e.g. WvW, killing groups of mobs, etc, a box pops up and says “Guild Wars 2 has stopped responding,” and I have the option to close it or wait for the client to resume responsiveness. The box pops up and goes away almost too quickly for me to respond. I don’t know what could be causing it. I’ve checked/updated my drivers, update any windows updates available, defragmented GW2, repaired the client, so on and so forth, and I don’t know what else could be done. Anyone else having a similar issue after the update? I’ll try to get a screenshot posted, but like I said, the box pops up and goes away almost too quickly for me to get a screenshot off. Thanks in advance.

You say you’re looking into this, but the last problem like this took two days to fix. This one has lasted almost if not over a month now. If the last problem was solved in two days, then what is the issue here? There are more major updates coming, and that’s great and all, but no one is going to want to play if you don’t address the “minor” bugs that aren’t so minor to us. I’ll gladly wait a week or two for new content if you just fix the kitten that matters to the players most.

This is still an issue. Fix this please. I just bought another chest piece in hopes that it would fix the issue, and it was still bugged, so I just wasted 2g. Attached is a screen of everything dyed Abyss, yet I have that stupid bright red accent. If this was supposed to be addressed 4 months ago, then it wasn’t fixed properly. Take care of it this time please.