Please upgrade your browser for the best possible experience.

Chrome Firefox Internet Explorer
×

Peculiar Resilience/Force Shroud Bug (attn bioware)

STAR WARS: The Old Republic > English > General Discussion > Bug Reports
Peculiar Resilience/Force Shroud Bug (attn bioware)
First BioWare Post First BioWare Post

KeyboardNinja's Avatar


KeyboardNinja
05.08.2013 , 03:23 PM | #1
Does anyone have any idea of why this would be happening?

Code:
19:19:43.736 Tam activates Resilience.
19:19:43.736 Tam gains Resilience.

19:19:46.368 Tam loses Resilience.

19:19:46.380 Titan 6's Huge Grenade hits Tam for 29789 energy damage, causing 29789 threat.
19:19:46.380 Titan 6 kills Tam.
I'm in tank spec, so I have a 5 second Resilience. I activated it at 19:43.736, and it apparently fell off at 19:46.368 (2.6 seconds later), coincidentally just PRIOR to the attack roll from Huge Grenade. And before you ask, it's easy enough to confirm that Huge Grenade is in fact a tech attack: http://www.torhead.com/ability/cBKqC0g/huge-grenade

I saw something similar a little later in the same HM S&V run:

Code:
19:53:55.796 Tam activates Resilience.
19:53:55.796 Tam gains Resilience.
...
19:53:58.074 Tam loses Resilience.
...
19:53:58.086 Operations Chief's Terminate hits Tam for 32360 energy damage, causing 32360 threat.
19:53:58.086 Operations Chief kills Tam.
Activated at 53:55.796, lost at 53:58.074 (2.3 seconds later), an instant prior to the attack roll which killed me.

My best theory at this point is that this is a rather odd consequence of the well-documented race condition in the engine's event handling. The more widely observed consequence of this race condition is the out-of-order logging that plagues combat logs everywhere.

Regardless of the source of this bug, it's annoying and really needs to be fixed. It's *literally* killing people, and if we had needed to burn a battle rez at some earlier point in the fight, it would have resulted in a wipe. I've anecdotally seen similar things with other cooldowns (Battle Readiness in particular), but I can't give evidence which is as definitive.

Incidentally, the full combat log for the above can be found here: http://www.torparse.com/a/215194
Computer Programmer. Theory Crafter. Dragonslayer on The Ebon Hawk.
Tam (shadow tank) Tov-ren (commando healer) Aveo (combat sentinel) Nimri (df scoundrel)
Averith (hybrid sniper) Alish (lightning sorcerer) Aresham (jugg tank)

Panzerfire's Avatar


Panzerfire
05.09.2013 , 11:17 AM | #2
Aha! I remember this happening, good thing torparse remembers your own logs cause I wouldn't have bothered going through 50+ documents to try and find the S&V ones. I knew I wasn't crazy when I thought the nade hit through shroud.

Quote:
21:38:20.372 Silentstorm activates Force Shroud.
21:38:20.373 Silentstorm gains Force Shroud.
------
21:38:22.408 Titan 6's Huge Grenade hits Silentstorm for 30735 energy damage, causing 30735 threat.
21:38:22.410 Titan 6's Huge Grenade effect of Huge Grenade fades from Silentstorm.
------
21:38:25.385 Silentstorm loses Force Shroud.

Same fight, working this time.

Quote:
21:35:31.065 Silentstorm gains Force Shroud.
21:35:33.757 Titan 6's Huge Grenade hits Silentstorm for 0 damage, causing 1 threat.
21:35:33.759 Titan 6's Huge Grenade effect of Huge Grenade fades from Silentstorm.
21:35:36.173 Silentstorm loses Force Shroud.

And managed to find another fight with the damage taken bug.
Quote:

22:37:16.782 Silentstorm activates Force Shroud.

22:37:16.782 Silentstorm gains Force Shroud.
----
22:37:17.664 Titan 6's Huge Grenade hits Silentstorm for 30293 energy damage, causing 30293 threat. (5724 absorbed)
-----
22:37:21.917 Silentstorm loses Force Shroud.
Link to first fight with bug: http://www.torparse.com/a/199503/6/0/Log
Link to second fight with bug: http://www.torparse.com/a/201569/11/0/Log

So fix this, and I guess we should use rakata medpack/overcharge saber or simply be topped off by the healers before it lands and/or sorc bubble.
Also, this only happened 3 out of the 30-40 or so force shroud/huge grenade sequences I looked at, could just be a random error.

MobileCover's Avatar


MobileCover
05.09.2013 , 06:23 PM | #3
While I am unable to currently link the logs I have also had this happen to me twice over the course of the 4 attempts it took our raid to down Titan 6.
Also sorry for the tangent, but while on the topic of Resilience. In TFB HM it doesn't cleanse the Corrosive Slime DoT, whereas in SM it did. Same with the Terror's scream, in SM it resists the damage but in HM I have only had it resist approximately 1 out of 10 instances of the scream damage. I have been unable to find anything that tells me whether this is intended or not.

grallmate's Avatar


grallmate
05.09.2013 , 07:55 PM | #4
Quote: Originally Posted by MobileCover View Post
While I am unable to currently link the logs I have also had this happen to me twice over the course of the 4 attempts it took our raid to down Titan 6.
Also sorry for the tangent, but while on the topic of Resilience. In TFB HM it doesn't cleanse the Corrosive Slime DoT, whereas in SM it did. Same with the Terror's scream, in SM it resists the damage but in HM I have only had it resist approximately 1 out of 10 instances of the scream damage. I have been unable to find anything that tells me whether this is intended or not.
I've found the same on my Shadow. I just assumed it was intended that Scream couldn't be resisted in HM to prevent Shadows from cheesing the mechanic. Ironically, it can now be reflected but still applies the debuff. I also noticed around 1.7 that Resilience wouldn't cleanse the Corrosive Slime like it previously had.

I haven't noticed the issue you outlined KBN but I haven't been tanking 55 Endgame on my Shadow since 2.0 hit. Guardian buffs ftw! :P
The Kae-Sare Legacy - The Harbinger
<Vindication> <Retribution>

Gralleh Grall'eh Khyar
Gralleh's Guide to Guardian Tanking [UPDATED for 2.0]

Grumpftard's Avatar


Grumpftard
05.09.2013 , 08:52 PM | #5
It has happened twice for me on Titan. I just attributed it to "Hmmpf...I musta just hit it too soon!" I thought it was just me.
TORVA NEX! (The Site) (The Video)
"You really don't have to say much more than that!"
Grumpf =Tankasin / G'rumpf =Mara / Gru'mpf =Jugg / Grum'pf =P-Tech
Grump'f =Shadow / Gr'umpf =Op Heals / Jei'Dahl =Merc DPS

Panzerfire's Avatar


Panzerfire
05.16.2013 , 05:44 PM | #6
Bump

/5char

Gyronamics's Avatar


Gyronamics
05.17.2013 , 04:09 AM | #7
Possibly wrong but I recall hearing at some point that anything which causes automatic misses is just increasing defensive stats so that normally, yes, it will miss/resist.

But if an attacker has enough accuracy it can get rolls which beat the defensive increase and let the hit through.
Hotwired @ Not Good Enough @ ToFN

WheresMyWhisky's Avatar


WheresMyWhisky
05.17.2013 , 07:23 AM | #8
Thanks for your post I have had this as well and just thought I had screwed up but having seen this thread I went back and checked my logs and have exactly the same as you on both titan 6 and Olok's terminate.

So I hope the devs look at this soon because as you say this must be killing a lot of shadows

/Bump

Ancaglon's Avatar


Ancaglon
05.17.2013 , 08:05 AM | #9
Quote: Originally Posted by Gyronamics View Post
But if an attacker has enough accuracy it can get rolls which beat the defensive increase and let the hit through.
NPCs, even bosses, aren't supposed to *have* accuracy over 100%. If these S&V bosses DO, then it is most certainly something that directly discriminates against Shadow tanks, because we have lower mitigation than our counterparts.

Kitru's Avatar


Kitru
05.17.2013 , 08:44 AM | #10
Quote: Originally Posted by Ancaglon View Post
NPCs, even bosses, aren't supposed to *have* accuracy over 100%. If these S&V bosses DO, then it is most certainly something that directly discriminates against Shadow tanks, because we have lower mitigation than our counterparts.
The devs have stated that they are capable of adding an "autohit" tag to an attack (Riposte has this tag for players), but they only use it for wipe mechanisms or things that players should *never* be able to resist (phase change control/damage effects). Most attacks against a tank *should* be able to be resisted, especially the attacks that are being mentioned here. It should also be mentioned that the bug isn't that Resilience isn't working; it's that Resilience is getting taken off *early*, right before the attack you want to avoid hits.
Walls of Text? I *love* Walls of Text!
My New Class Idea
Shadow Class Rep - Suggest/Review Questions Here
Quote: Originally Posted by Fende View Post
Listen to Kitru. Kitru knows all.