Guild Wars 2

I hate posting warrior specific stuff here, but that profession thread blankets things too quickly.

I have found that you can be immobilized when using whirlwind. It appears to hit right after the trait “Mobile strikes” checks and cleanses the current immobilize and the evasion mechanic for whirlwind kicks in.

My proposal is to for example make “Mobile Strikes” :

“Movement skills break immobilize and you are immune to immobilize for the duration of the movement skill.”

Honestly what is the point of Mobile strikes if you can be immobilized before whirlwind, mid eviscerate, right after you cast rush, mid earthshaker, etc.

Maybe this is too strong. But I am not considering chill or cripple here. Just want the immo off when I expect it off.

Although I see why you’d want this changed I don’t really like the idea. Usually I try my best to reactively use Chains of Light to snare a Warrior when using one of these abilities, so I can get them mid bulls, etc. It punishes those who spam immobilize to a degree because they will pre-emptively use immobilize but it rewards when they randomly hit it which is an unfortunate side effect of having no mana/energy pool in this game.

If you change this mechanic to the one you’re suggesting then you reward the Warrior’s bad play, immobilize will effectively have no use against a Warrior. I am extremely against that.

I’m not against Warriors getting a teleport skill though. Maybe that could be something to look into?

I gotta agree with K Pop, for a 20 point trait it’s way too unreliable.

Agree with K Pop as well … but I completely understand where Silven is coming from. Possible to agree with both?

The original poster surely means Rush, as Whirlwind would make you evade any immobilize thrown at you anyway during its brief duration.

Med.6150:

The original poster surely means Rush, as Whirlwind would make you evade any immobilize thrown at you anyway during its brief duration.

This has proven false because I have been immobilized as I stated in the description. There seems to be a window of opportunity and it was by the guardian chains.

Why is being immune to immobilize promoting bad play?
Movement skills are all about 8sec minimum cd for war with durations max of 2 seconds. Considering we cannot teleport, this would just make the gap closer more reliable.
It is not like we can spam movement skills as if it is on an initiative system.
It is not like we would be immortal to slows conditions or direct damage.

The trait just does not do its job at times.

Immobilizes are rarely instant enough to use in counter to something like an eviscerate.
It could be a nifty tweak though.

I think, that for a class already suffering from being kited, it is not a welcomed tweak, how nifty it might be
But from the one executing a nifty tweak, I can see the reward in executing it.
In the current state, taking the view of the warrior, would perhaps be the appropriate approach?

To people who reply that things don’t happen, I have put enough hours on the war and I facepalm when random immobilizes hit after my movement skills start.

I am not making these things up, they have happened at some point and time.

I hate random immobilizes but it’s not going to be any good when you nerf people who are actually using it correctly. Making immobilize ineffective against Warriors doesn’t seem like a good solution to the random immobilize problem.

Completely agree with you right now that trait is not worth using because usually I get hit with immo while using rush or what not which I need to escape fights (glass warr). Oh yea and protection on dodge and some good condi removal would be nice

Jax.5261:

I hate random immobilizes but it’s not going to be any good when you nerf people who are actually using it correctly. Making immobilize ineffective against Warriors doesn’t seem like a good solution to the random immobilize problem.

This would only be if you trait into it.

Counter example to your statement: What about all the traits that remove conditions periodically or per activation fulfilled. Should we remove those because they counter skillful condition application?

I am not downplaying people’s skill but I imagine it like this scenario:

I cast eviscerate (0.75s skill) Mobile Strike checks and clears immobilize as I am leaping. You have to recognize my animation and realize it is my burst skill. You then proceed to cast an immobilize on me. Let’s Assume it takes a (0.25sec) to recognize and react to my action. That leaves (0.5s). You then proceed to cast and immobilize which must have less than (0.75s cast to be safe) (0.5s cast). Said immobilize hits me before I reach my target and effectively stops my burst.

I think this is best case scenario to support a skillful play but seeing as it is less than (0.75s) window, I am led to believe it is more randoms…