Swirling Winds bug

Swirling Winds bug

in Bugs: Game, Forum, Website

Posted by: Mem no Fushia.7604

Mem no Fushia.7604

It destroy projectiles, but cannot destroy unblockable projectiles.
Unblockable projetiles mean they can’t be blocked it doesn’t mean they cannot be destroyed.
Becouse description of Swirling Winds only states it destroy projetiles. So I consider it as bug, becouse unblackable projetile is still projetile.

Swirling Winds bug

in Bugs: Game, Forum, Website

Posted by: RoseofGilead.8907

RoseofGilead.8907

https://wiki.guildwars2.com/wiki/Unblockable

“Unblockable is a property of attack skills which prevents the attack from being blocked, and in case of ranged attacks, reflected or otherwise destroyed by effects of skills.”

I’m pretty sure that’s just working as intended.

Swirling Winds bug

in Bugs: Game, Forum, Website

Posted by: Mem no Fushia.7604

Mem no Fushia.7604

Ok. If wiki states that. Can someone check if it work equal for all skills that destroy projetiles to not destroy unblockable ones? For example corrosive cloud etc, becouse something rings that I encountered unblockable projetile being destroyed.

Swirling Winds bug

in Bugs: Game, Forum, Website

Posted by: Illconceived Was Na.9781

Illconceived Was Na.9781

Like a lot of jargon in this game (or others for that matter), “block” and “unblockable” are sometimes used rigorously and sometimes not. The wiki has a long list of so-called projectiles that cannot be reflected as well as non-projectiles that end up being reflected as if they were projectiles.

Similarly, some blocking skills won’t prevent certain other skills from hitting and some “unblockable” skills can be blocked under certain circumstances.

This isn’t necessarily to do with any mechanical bug, but more in the way that there’s a difference between technical English and spoken English. Just as biologists distinguish between spiders and insects, while most people could care less about the difference.

Further, sometimes we perceive that an unblockable is being blocked (or an unreflectable is being reflected), when it turns out to be some other skill involved, but we just read the UI wrong due to latency (of the game or of the brain).


All that said, review the combat log to confirm that your perception is accurate and then use the in-game /bug reporting tool so that ANet can see the specific circumstances. In some cases, they’ll update the description to reflect how things work in game; in others, they will update the skill(s) involved; and in others, they’ll just confirm that, hey, the game isn’t 100% consistent for various good (and bad) reasons.

John Smith: “you should kill monsters, because killing monsters is awesome.”

(edited by Illconceived Was Na.9781)