more specific??? When i have to type /dance in order to re-gain control of my character or else its just stuck in place. Happens to thieves and eles who trigger evade/dodge/blink same time as immobilization goes off. Its been around for ever and they even tried to patch it awhile ago, still broken.
more specific??? When i have to type /dance in order to re-gain control of my character or else its just stuck in place. Happens to thieves and eles who trigger evade/dodge/blink same time as immobilization goes off. Its been around for ever and they even tried to patch it awhile ago, still broken.
Happens to me sometimes on my warrior, which doesn’t have a blink, so I have no idea what could cause it, but it is indeed annoying. I usually just use a leap to get out, but if it’s on cooldown in an intense fight, it usually means my certain death.
It is not what you do, but how and why you do it that counts.
I notice sometimes after building a ram, i cant move afterwords for like 10-20 seconds. Most times i don’t experiance it. It’s happened a few times when an enemy zerg is attacking, and thats not good.
all the players in wvw should have a 5 seconds immune on each 5 seconds of immobilize ( i think the most time on immobilize skills is 4 seconds ) , to prevent all these traits/environment bugs/exploits .
a mesmer once immobilized me for over 20 seconds , saved me defy pain and defiance stance , but for only 20 sec…. no stability skill and no berseker stance worked under this exploit, it reapplied instantly ……
He is talking of the invisible immobilise bug like when you are building siege and get stuck in it I think – not the actual condition.
I can only speak from heavy classes played without blink/teleport but it seems to happen when you get “stuck” on warbanners or engy turrets or siege when they are thrown right on top of you at a certain time.
But yes, it’s been a problem for over a year now in my experience and still no-ones sure what causes it.
For me a weapon switch usually fixes it, when I got stuck after building siege. I have yet not experienced being stuck after immobilize wore off.
there’s the bug where you get stuck on siege, and then there’s another, rarer, bug where after blinking or leaping (apparently at the same time as being immobilized) your character gets stuck and you can’t move or turn until you do an emote.
It hapens when u try to cure ur immob instantly after u get it (reaction time or pure luck of 0.1 seconds) thus removing the immob condition tag from ur hotbar but ull still be stuck.
The siege stuck bug is also pretty cool, but noone playes wvw for dropping siege anymore … do they? :P
It’s 2 types of people who are still in wvw, the ones who are trying to look for gvgs or the ones in EOTM brainlessly running through keeps for karma.
For me a weapon switch usually fixes it, when I got stuck after building siege. I have yet not experienced being stuck after immobilize wore off.
there’s the bug where you get stuck on siege, and then there’s another, rarer, bug where after blinking or leaping (apparently at the same time as being immobilized) your character gets stuck and you can’t move or turn until you do an emote.
And then, there is the bug forum.
Tin Foil [HATS]-Hardcore BLTC-PvP Guild
Bloin – Running around, tagging Keeps, getting whack on Scoobie Snacks.
For me a weapon switch usually fixes it, when I got stuck after building siege. I have yet not experienced being stuck after immobilize wore off.
there’s the bug where you get stuck on siege, and then there’s another, rarer, bug where after blinking or leaping (apparently at the same time as being immobilized) your character gets stuck and you can’t move or turn until you do an emote.
For me a weapon switch usually fixes it, when I got stuck after building siege. I have yet not experienced being stuck after immobilize wore off.
there’s the bug where you get stuck on siege, and then there’s another, rarer, bug where after blinking or leaping (apparently at the same time as being immobilized) your character gets stuck and you can’t move or turn until you do an emote.
For me a weapon switch usually fixes it, when I got stuck after building siege. I have yet not experienced being stuck after immobilize wore off.
there’s the bug where you get stuck on siege, and then there’s another, rarer, bug where after blinking or leaping (apparently at the same time as being immobilized) your character gets stuck and you can’t move or turn until you do an emote.
Well, those who are responsible to fix the bugs dont read the wvw forums. So why open a topic here, if a topic on this bug already exists?
I’m guessing you missed the fact that post was written over a year ago and yet you still try to make it seem like the OP is in the wrong for posting it here. I’ve just shown you that posting in any forum doesn’t make a difference. That post was made a year ago, and yet here we are, all experiencing the same bug.
It is not what you do, but how and why you do it that counts.
For me a weapon switch usually fixes it, when I got stuck after building siege. I have yet not experienced being stuck after immobilize wore off.
there’s the bug where you get stuck on siege, and then there’s another, rarer, bug where after blinking or leaping (apparently at the same time as being immobilized) your character gets stuck and you can’t move or turn until you do an emote.
Well, those who are responsible to fix the bugs dont read the wvw forums. So why open a topic here, if a topic on this bug already exists?
I’m guessing you missed the fact that post was written over a year ago and yet you still try to make it seem like the OP is in the wrong for posting it here. I’ve just shown you that posting in any forum doesn’t make a difference. That post was made a year ago, and yet here we are, all experiencing the same bug.
I didnt miss that the other post was over a year ago. And just because it hasnt been fixed yet doesnt mean that all bugs, no matter where they are posted, dont get fixed.
This subforum looks more and more populated by people that just come here to qq because they know that dev/mod attention is minimal.
Just give me 1 good reason why someone should post a bug report here.
Tin Foil [HATS]-Hardcore BLTC-PvP Guild
Bloin – Running around, tagging Keeps, getting whack on Scoobie Snacks.
For me a weapon switch usually fixes it, when I got stuck after building siege. I have yet not experienced being stuck after immobilize wore off.
there’s the bug where you get stuck on siege, and then there’s another, rarer, bug where after blinking or leaping (apparently at the same time as being immobilized) your character gets stuck and you can’t move or turn until you do an emote.
Well, those who are responsible to fix the bugs dont read the wvw forums. So why open a topic here, if a topic on this bug already exists?
I’m guessing you missed the fact that post was written over a year ago and yet you still try to make it seem like the OP is in the wrong for posting it here. I’ve just shown you that posting in any forum doesn’t make a difference. That post was made a year ago, and yet here we are, all experiencing the same bug.
I didnt miss that the other post was over a year ago. And just because it hasnt been fixed yet doesnt mean that all bugs, no matter where they are posted, dont get fixed.
This subforum looks more and more populated by people that just come here to qq because they know that dev/mod attention is minimal.
Just give me 1 good reason why someone should post a bug report here.
You’re right, posting a bug here will amount to nothing. There hasn’t been a dev response here in ages, bugs have been in wvw since release. What I don’t get however is why somebody posting a bug here could ever annoy you, which it evidently has. Why you still think that posting in a different sub forum would make a kitten bit of difference. And why, despite all that, you still seem to have the need to somehow defend Anet by saying it may get fixed in the future, when that future is today for the people complaining about it a year ago.
I do agree with you however. This post may be in the wrong sub-section. This post will amount to nothing. However, posting in the bugs section seems to produce the same result. Although if you’re lucky, just lucky, you may get that dev response saying they are looking into it, it will get fixed. Yet here we are, with this and many other bugs still here after months and years of waiting on those words.
Reporting a bug in any forum seems to get the same copy pasted replies, so telling somebody to put it in a different sub-forum is pointless, as they all, lead to the same thing.
It is not what you do, but how and why you do it that counts.
Someone dug up a thread with a dev response that said they are trying to pin it down. That was a year ago hahaha.
This seems like a top priority bug and it clearly has not been. This should be at the top and if it’s a hard fix that involves time it should’ve been invested in way before this point.
