Last edited by Yup; 12-14-2017 at 02:53 AM.
Devs - weird bug just popped up in pvp. Was playing when my Astra was killed. Revived her with VHE and none of her attack’s would hit the enemy. Perfect hit it or not every time she attacked it just showed “miss” all over the screen and the enemy took no damage. I revived her twice actually and same thing she could not land a hit.
They were not invincible and negative effects would still proc (permadeath) but no damage.
Luckily I won the match but it took nearly 10 minutes.
Last edited by Ezz; 12-14-2017 at 05:59 AM.
Sparton - I just got my first MACL12 since reset on LoL, after dozens of runs. I checked my shard count and was at 993 3* shards in one stack. My belief is that the run generating the error would have dropped >6 of them. This would support the "write to two different stacks" theory.
Well crap. My Tailgunner Eddie disappeared at some point. I know I wouldn't sacrifice a non dupe Eddie. Hopefully I can get him back at some point... I wanted to use him before but now... dang! He could be a beast!
Also, Really excited to see a fix for counter/revenge... By far the worst bug that ever occurred lol
Last edited by Dank Brew; 12-14-2017 at 06:40 PM.
Hey Sparton, will the Tailgunner Eddie “Roar” Skill change also apply to Soldier Eddie who has the same skill?
i'm pretty sure macl12 in LOL is related to shard splitting. as i used my red shards game never crashed again. unfortunatly the next two days gave me clean 999 shards, so there was no shard splitting involved. i really wanted to prove this theory, but the game didn't let me this time. next try on sunday... but in fact the only two lol crashes i had, happend as i had 995 3* red shards. and i played A LOT lol this week (11 droids). so very little doubt in this theory.
k, Thanks for the confirmation. I'll work with our QA to ensure a bug is entered in our system to track this; your theory may be right, but it's hard to tell from the transaction history I have access to.
It will; I'll update our final tuning notes table to reflect that.
I don't suppose you happen to recall when approximately you tipped over to 999 on a stack, do you? Seeing that in your transaction history may help with eliminating some possibilities for how the bug is occurring.
Just to confirm, did that match conclude around the time you posted that?