July 2020
Product: Star Wars: Galaxy of Heroes
Platform:Android Phone
What type of device are you experiencing the issue with? Galaxy S10
OS Version Android 10
Ally Code: (Find it here: http://bit.ly/AllyCode ) 578872959
What type of issue do you have? Gameplay
How often does the bug occur? Every time (100%)
Summarize your bug My arena shard is full of Sith Empire + GBA teams. Whilst using 501st, if one of my clones has Exposes/Shock on them when they die, it doesn't trigger 5s sacrifice properly. This causes me to lose both clones, instead of the original target surviving with the updated stats. I'm sick and tired of losing because of your unintended interactions.
Steps: How can we find the bug ourselves? Take a 501st team w/ General Skywalker + 4 Clones (Fives, Rex, Arc, Echo), and fight Darth Revan, Malak, Bastila Fallen, and Geo Brood alpha. Eventually, you'll have GBA AOE and apply exposes across your team, and you can watch the 'magic' happen for yourself.
Connection Type Wifi
Please select your region North America
Country Canada
This bug is highly annoying, and causes arena losses. Please fix it.
Solved! Go to Solution.
July 2020 - last edited July 2020
@SWGoYeti Nope, it's 20% of the max health of the target. All percentage based health attacks are based on a target's max health.
Using your example then, the expose damage occurs first, causing the sacrifice. Health regain is prevent due to shock. Target clone dies due to attack damage that follows, and Fives dies due to the sacrifice being proc'd.
As stated, this seems to be working as designed for attacks with multiple damage instances. If you can grab a video of this happening it can help the team investigate if they feel there is a bug. They are back in the office tomorrow.
July 2020
July 2020
Have you read what I've actually wrote?
This is not about shock blocking health regain. This is about an interaction between shock/exposes that cause the sacrifice to not properly function.
Might I suggest, perhaps, that before replying in the future you read what is in the actual bug report. Thank you.
July 2020
July 2020
@SWGoYeti wrote:
Have you read what I've actually wrote?
This is not about shock blocking health regain. This is about an interaction between shock/exposes that cause the sacrifice to not properly function.
Might I suggest, perhaps, that before replying in the future you read what is in the actual bug report. Thank you.
Thanks, I did read your report. It was fairly vague about what was happening and what "not sacrificing properly" means. Quite frequently we have to make educated guess about what players are reporting, and try to answer based on partial information.
As Christoph said, if shock prevents the heal, subsequent damage from DR Secondary attack and/or expose may be sufficient to kill the primary target. This would match what you are reporting.
Is that what you are actually seeing? If not, please provide more details or share a video or screenshot to help us understand what you're trying to report. We are here to help!
July 2020
The expose removes 20% of CURRENT health, right? Not Max health? And why wouldn't the expose damage land first? It's suppose to trigger when attacked, which should layer its damage hit first, no?
July 2020 - last edited July 2020
@SWGoYeti Nope, it's 20% of the max health of the target. All percentage based health attacks are based on a target's max health.
Using your example then, the expose damage occurs first, causing the sacrifice. Health regain is prevent due to shock. Target clone dies due to attack damage that follows, and Fives dies due to the sacrifice being proc'd.
As stated, this seems to be working as designed for attacks with multiple damage instances. If you can grab a video of this happening it can help the team investigate if they feel there is a bug. They are back in the office tomorrow.
July 2020
Hi @SWGoYeti thanks for the report.
From your description, it sounds like @ChristophIV and @GladOS-013 are correct in what they are saying.
If you can provide video of the issue you are describing, we could look into this further otherwise, it sounds like its working as intended.