Guild Wars 2

- Loses line of sight behind wisps and just stands still forever
- Loses buff but stays invulnerable, cannot fix without leaving the instance completely and resetting
- Hitbox seems to be wonky, some attacks the animation vs hitting is out of sync

We did T2 Bloomhunger earlier, and it seems that after you wipe on him once, you cannot place the wisps in wisp clefts on any subsequent attempts. All members of the party would pick up the wisps and try to place them in the clefts during the last phase — and none of us would be able to interact with the clefts, causing a wipe. On one attempt, we couldn’t even place the wisp in the beginning to remove Bloomhunger’s initial invulnerability due to the same issue.

The only solution was to leave the fractal completely, resetting it and starting over from the beginning.

Could this please be looked into? Thank you.

I was running T3 Swampland Fractal (lvl 56) yesterday and couldn’t finish it due to a bug at the Bloomhunger boss fight. The wasps wouldn’t interact with the clefts. We had the group wiped multiple times and it still wouldn’t work. This happened a few times at the beginning of the fight and didn’t work at all when Bloomhunger was at 25% health. After getting into a new instance, it seemed to have worked fine. Thus, I assume it only occurs if you get a bad instance by some unfortunate chance.

Had the same problem at 77 just now. The first time we got it to 25% I managed to get a wisp in, but after wiping (not everyone else got one in), the receptacle stumps couldn’t be interacted with anymore.

This is still happening right now. Couldn’t finish because of it.

Same for me here. Is this going to be fixed ?

Just wiped from this. Party wiped once because one person died getting to the wisp, and after that we got wiped because we couldn’t interact with the stump during the “kill phase”.

In another thread about this bug, a player suggested this could be reproduced if a single person pulled a wisp out ‘toon soon’, i.e. before the ‘task advice’ message in the upper right corner of the screen updated (apparently, there’s a delay). Successful and abject failure groups don’t notice, because in both cases, all four wisps are in the same state (either placed correctly and not even started). Partially successful groups notice because (so the theory goes) the wisps are in different states and the game has trouble figuring out what to do.

It’s an annoying bug either way for players. The difference is: it might be preventable (same as the former bug of getting ahead of Rox/Braham was). (And of course, Anet should fix it sooner rather than later.)

Illconceived Was Na.9781:

It’s an annoying bug either way for players. The difference is: it might be preventable (same as the former bug of getting ahead of Rox/Braham was). (And of course, Anet should fix it sooner rather than later.)

Just ran into that bug today.