silverkeltMember, NW M9 PlaytestPosts: 4,235Arc User
I can recreate it in and out of party.. some of speculated it is reacting to certain proc feats on other classes.. and maybe? but you do not HAVE to be in party to get it.
I swear the game knows when you need it the most.. and then gives you the bug =P .
0
instynctiveMember, NW M9 PlaytestPosts: 1,885Arc User
In the Q&A I think I read something about lag-related and difficult to solve... I hear the same often... at work :-) So tricky, not my code, bad documentation, must be processor bug...
Okay. So this will become a feature? You can add "a chance" into the description of the Unstoppable tooltip. Why? Ah... balance issue! Problem solved.
I had this happen to me again today in a skirmish on LB and it was hella frustrating. Pls guys, its a core mechanic for GWF and should be up-voted to highest priority for next update. Thx
I still get it. I get it mostly when in Heroics where my temp hit-points don't get drawn down (hit by mobs) and unstoppable gets stuck. I have to get hit on purpose to make it get unstuck to use it again and hope I survive the hit.
I was finally able to repro this on my own and have sent the exact steps to the devs. Thank you for all the help.
That was December 2015 Now we have December 2016 soon
They simply ignored it because it is too hard to fix. Right?
I dont remember the exact words they use for everything that isnt fixed yet, but they were something like "we dont spend workhours for something that will not give us something back" ....i guess that covers you..
An anecdote also says "They want the whole pie untouched and the dog's belly full", in other words they dont respect the money or time we spend to this game, never did never will i guess.
0
plasticbatMember, NW M9 PlaytestPosts: 12,439Arc User
I get used to it so bad that when it happens, I run to red and yell spank me, spank me but not too hard.
*** The game can read your mind. If you want it, you won't get it. If you don't expect to get it, you will. ***
I've noticed that while I am Unstoppable and waiting for the Determination bar to be at the bare minimum to deploy another IBS and refill the Determination bar again that the bar doesn't empty. It just start filling again. Like it forgot to empty. When that happens (and this is a guess) the game doesn't realize we are not Unstoppable anymore and is still waiting for the cooldown. Hence we are stuck. How does TempHP fit into that is for @terramak to discover.
I've noticed that while I am Unstoppable and waiting for the Determination bar to be at the bare minimum to deploy another IBS and refill the Determination bar again that the bar doesn't empty. It just start filling again. Like it forgot to empty. When that happens (and this is a guess) the game doesn't realize we are not Unstoppable anymore and is still waiting for the cooldown. Hence we are stuck. How does TempHP fit into that is for @terramak to discover.
I 100% agree.
There are several states, implicitly or explicitly expressed with 3 variables or more.
First variable (#1) indicates if Unstoppable active or not. It role to prevent another Unstoppable to activate. It should be reset at moment when Unstoppable (#4) reaches zero value.
Unstoppable combat effect/visuals are driven by second variable (#2), gradually reduced by client timer task.
Third variable state enables to gain Unstoppable (#3). It work with junction with second, probably it is just statement #2 != #3.
GWF Unstoppable level is obviously some forth numeric value (#4). It initiates Unstoppable and it second condition (#4 > 0 => #2 = true, #3 = false), but first variable condition (#1 = false) should be met as well.
The bug is self-recoverable once default out-of-combat timer reduces Unstoppable (#4 = 0) to zero and this resets first variable (#1 = false).
For some reason (probably due the state is affected by different threads and the modification is not thread-safe), you get condition #1 = true, #2 = false, #3 = true.
@terramak, i think you or your team should have all you need to fix.
Let me bump this again since a new version of the game came out and this bug is still active and present. (the new version didn't magically fixed it).
I know it's silly to ask, but can we get any info if this is going to be looked at in the near future? I know you are aware of it, but you have been aware of it for some time now and for a class mechanic to be broken this long is just silly. @terramak
And let me tag @mimicking#6533 also since he might not be aware of this old thread.
And it's annoying because it does tend to happen right when everything is going on and things are proccing left and right... right when you need it the most to work, it doesn't.
I wouldn't hold my breath for a fix, resources are being spent on the aftermath of keygate and figuring out how to make fishing a more tedious grind. The small population affected by this bug isn't significant enough to warrant serious investigation.
The games core mechanics are broken and you are releasing updates and patches (unimportant details very often) ... hey ... some legacy code need a functional review here!
Unfortunately this thread will not get to see his 2 Year Anniversary.
I would like to thank every single person that contributed to this thread over the (almost) years. The bug has finally been squashed as said in the live stream and it should soon see the light of day.
I would love to say to the moderators they can finally close this beast but let's hold it off for just a bit longer till everything falls into place.
I wont´t believe this! The beloved thread! Dead?! Oh no!
Great! Finally! Let´s see if they got it.
When you read the release notes there is some... bad feeling... something like "now there is an ugly delay between end-of-unstoppable and determination gain for the next one." Maybe there is a chance my thread will see his 2nd aniversary ;-)
Even if not, the bug itself is 2 years old... ATM it feels more like a feature... a side effect... some randomness to spice the usual GWF gameplay *g*!
Comments
I swear the game knows when you need it the most.. and then gives you the bug =P .
And yes, it has happened both while I'm solo (with no one around for miles (on SH map)), with and without temp HP.
I know this is on the Dev's radar, and will be difficult, if not impossible, to track down because it is so intermittent.
"...I grab my wiener and charge!" - ironzerg79
Okay. So this will become a feature? You can add "a chance" into the description of the Unstoppable tooltip. Why? Ah... balance issue! Problem solved.
so, this bug is still here just so you know.
I get it mostly when in Heroics where my temp hit-points don't get drawn down (hit by mobs) and unstoppable gets stuck.
I have to get hit on purpose to make it get unstuck to use it again and hope I survive the hit.
Now we have December 2016 soon
They simply ignored it because it is too hard to fix. Right?
An anecdote also says "They want the whole pie untouched and the dog's belly full", in other words they dont respect the money or time we spend to this game, never did never will i guess.
I've noticed that while I am Unstoppable and waiting for the Determination bar to be at the bare minimum to deploy another IBS and refill the Determination bar again that the bar doesn't empty. It just start filling again. Like it forgot to empty. When that happens (and this is a guess) the game doesn't realize we are not Unstoppable anymore and is still waiting for the cooldown. Hence we are stuck. How does TempHP fit into that is for @terramak to discover.
There are several states, implicitly or explicitly expressed with 3 variables or more.
First variable (#1) indicates if Unstoppable active or not. It role to prevent another Unstoppable to activate. It should be reset at moment when Unstoppable (#4) reaches zero value.
Unstoppable combat effect/visuals are driven by second variable (#2), gradually reduced by client timer task.
Third variable state enables to gain Unstoppable (#3). It work with junction with second, probably it is just statement #2 != #3.
GWF Unstoppable level is obviously some forth numeric value (#4). It initiates Unstoppable and it second condition (#4 > 0 => #2 = true, #3 = false), but first variable condition (#1 = false) should be met as well.
The bug is self-recoverable once default out-of-combat timer reduces Unstoppable (#4 = 0) to zero and this resets first variable (#1 = false).
For some reason (probably due the state is affected by different threads and the modification is not thread-safe), you get condition #1 = true, #2 = false, #3 = true.
@terramak, i think you or your team should have all you need to fix.
— (The unwritten rule)
I know it's silly to ask, but can we get any info if this is going to be looked at in the near future? I know you are aware of it, but you have been aware of it for some time now and for a class mechanic to be broken this long is just silly.
@terramak
And let me tag @mimicking#6533 also since he might not be aware of this old thread.
And it's annoying because it does tend to happen right when everything is going on and things are proccing left and right... right when you need it the most to work, it doesn't.
I wouldn't hold my breath for a fix, resources are being spent on the aftermath of keygate and figuring out how to make fishing a more tedious grind. The small population affected by this bug isn't significant enough to warrant serious investigation.
I would like to thank every single person that contributed to this thread over the (almost) years.
The bug has finally been squashed as said in the live stream and it should soon see the light of day.
I would love to say to the moderators they can finally close this beast but let's hold it off for just a bit longer till everything falls into place.
Thank you everyone.
Great! Finally! Let´s see if they got it.
When you read the release notes there is some... bad feeling... something like "now there is an ugly delay between end-of-unstoppable and determination gain for the next one." Maybe there is a chance my thread will see his 2nd aniversary ;-)
Even if not, the bug itself is 2 years old... ATM it feels more like a feature... a side effect... some randomness to spice the usual GWF gameplay *g*!
See u soon (or better not)
//Bellistor