Guild Wars 2

While pushing the core around I (Druid) normally utilize quickdraw + LB4 to quickly push the core through the second and third rift and having our mesmer(s) finish via curtain pull into the fifth one.

This, for whatever reason, did not work yesterday. I could push the core around normally via Staff 1 but switching to longbow resulted in one of two cases:

- LB4 would not move the core at all
- LB4 would move the core roughly as far as a Staff/LB auto would have done

This odd behaviour caught me and my raid off guard. While I did “fine” pushing the core around it was a LOT more stressful than I was used to prior.

Considering the already odd behaviour of KC’s core for the most part (i.e. icd on movement) I have to wonder whether or not this is actually intended or yet another bug with the fight.

O.T.: thanks for fixing the door.

Edit: Before someone asks: I traited for “Lead the Wind” for piercing arrows.

I don’t know if they fixed the other bug which causes the orb to get stuck or not yet.

I’ve notified them of it getting stuck in specific areas on that map but that issue to the best of my knowledge still existed up to the last balance patch.

There are specific spots where the orb will get glitched on the terrain. You probably hit one of those spots. This bug existed since wing 3 launch.

The push mechanic on the orb has an in-built cooldown of 2 seconds. If you strike the orb with a CC skill that deals damage, and that CC skill activates the in-built push mechanic, it will use the push mechanic instead of your CC skill. This same problem happens if you mistime Glyph of Tides or Mesmer GS 5. The only reason Mesmer Focus pull works reliably is because it does not do damage, which means it never risks triggering the in-built push mechanic.

tl;dr: You mistimed your LB4 and it activated the in-build push mechanic instead of LB4’s actual push.

As for your other issue, there are certain locations on the floor where the orb will get stuck and not push. It can sometimes be hard to avoid these (and knowing where they are just takes practice) and ANet should really fix them to not exist, but they’ve been around a while and can be worked around.