Anakin Eta-2 bug
Product: Star Wars: Galaxy of Heroes
Platform:Android Phone
What type of device are you experiencing the issue with? OnePlus 3T
OS Version Android 7.1.1
Ally Code: (Find it here: http://bit.ly/AllyCode )
What type of issue do you have? Gameplay
How often does the bug occur? Every time (100%)
Summarize your bug There is a bug which allows ships to survive after the first attack that would kill them even after Unending Loyalty buff expires in battles against Negotiatior.
Steps: How can we find the bug ourselves? Just play ships arena against Negotiator team.
Connection Type Wifi
Please select your region Europe
Country
Hi there CG!
It seems that during your new campaign for introduction of new ships you broke some of the existing ones.
I'd like to point out that after the patch introducing Hyena and Y-Wing a serious damage bug appeared. The bug is in the incorrect damage calculation after the expiration of Unending Loyalty buff. Mostly it is an issue in the early stages of battles against Negotiator but it seems it happens also on later stages of said battles.
Here is a video explaining the bug: https://www.youtube.com/watch?v=aM9cOXUuhEw
As we can see enemy Eta-2 has 97786 protection and 27747 health. After I "killed" it once Unending Loyalty triggers and Eta-2 has (as per Unending Loyalty description) 13874 protection (50%) and 25424 health (26% from total) which results in 39298 points of summarized vitality. At 0:39 of my video you can see me using Impending Assault ability of my Anakin's Eta-2. It crits for 67685 damage which should be more than enough to kill enemy's Anakin Eta-2. But as you can see it survives the attack.
Prior to the pach that introduced Hyena and Y-Wing said Eta-2 would had been killed.
I tested it more than once even with very weak Anakin Eta-2 and even stronger damage (80k+), it still survives the first attack after Unending Loyalty expires.
Will you please fix this notorious bug asap?
Thank you in advance.
- @StuG_III_ausf_G Hey, thanks for the report. We actually fixed that bug (but haven't updated the developer tracker yet). I looked at your video and also tested it myself and can confirm the issue is fixed now.
The source of confusion is that in your calculations you assumed that the Protection Up buff is based off the Max Protection of the character, whereas Protection Up buff is always based off of Max Health.
Hope this clarifies the issue. Thank you.