Guild Wars 2

I posted this in the bug section it has been buried with no responses.

The champion instigator in Southsun can cast a burn condition called burning pitch on players that does not get cleansed by elixir c or its toolbelt skill. All other condition removal skills still work. I think the problem is that elixir c converts conditions into boons and because this burn condition is named differently, the skill does not know how to convert it.

It’s not just the Instigator, a lot of event-inflicted conditions in Southsun can’t be cleansed normally. I used the bug report function, hopefully it gets fixed in.. the next year, given how long Scope is taking.

If you’re curious to what I’m seeing, go get poisoned by the Reef Drake Broodmother near the Crab Toss arena. Super Elixir and Drop Antidote don’t seem to cleanse it 90% of the time for me, despite hearing a distinct cleansing sound upon picking up the antidote. It goes away though once she hits me with one tick of her flame breath, although I think that’s part of her skill, what with it saying ‘Immolates poisoned foes’ and all that.

I think the Broodmother uses the same mechanic as the poison/flamethrowers available in the weapons crate, where when you get poisoned, the second attack reacts for extra burning damage.

There has long been the hatched Karka thing, and THOSE conditions don’t get cleansed by anything either, they will blind you, slow your mobility and one other condition and I have tried the new heal turret (>.<), Elixir C, Formula 409, and non of these removes any of the new conditions…

What is the point of having condition removal in your build if they keep adding conditions that are immune?

lunyboy.8672:

I think the Broodmother uses the same mechanic as the poison/flamethrowers available in the weapons crate, where when you get poisoned, the second attack reacts for extra burning damage.

There has long been the hatched Karka thing, and THOSE conditions don’t get cleansed by anything either, they will blind you, slow your mobility and one other condition and I have tried the new heal turret (>.<), Elixir C, Formula 409, and non of these removes any of the new conditions…

What is the point of having condition removal in your build if they keep adding conditions that are immune?

The Alien facer#p# is not a condition, the same way Soothing Mist is not a boon

They are…. IDK… but definitely not condition. And definitely horrifying

it’s only a matter of time before they change the whole facer#p# thing to give a condition: Injected.
“Within 30 seconds, a young karka will burst out of victim’s stomach. All nearby allies will be FEARed for 10 seconds, victim will die instantly”

thought it was pretty obvious you have to do a barrel roll to get the lil leeches off you

idk just makes sense

Raestloz.7134:

The Alien facer#p# is not a condition, the same way Soothing Mist is not a boon

They are…. IDK… but definitely not condition.

Exactly, but they are the same color and shape as a “normal” condition indicator, placed on the bar the same way, and when you roll over them, give the same type of information about their effects. Soothing Mist at least has a different look on the UI so it is not obviously mistaken for a boon.

It is a basic failure of User Interface to co-mingle status indicators without differentiation when they need different tactics or skills triggered to remove them. Agony is the same way, it shows as a condition on your bar, but can’t be cleansed or removed, but must be resisted, or depending on the mechanic, you must dodge, or otherwise block the initial application. The magenta spikes poking out of your toon obviously indicate that you are being Agonized, but it is still a bit sloppy.

Some consistency here would be useful is all I am saying.