Sith raid damage bug!

Anyword on when this masty bug will be fixed?

Replies

  • StarSon
    7572 posts Member
    Options
    No!
  • Darthpedro
    1175 posts Member
    Options
    What bug
  • TVF
    36860 posts Member
    Options
    https://forums.galaxy-of-heroes.starwars.ea.com/discussion/167687/content-update-4-25-2018
    Ongoing Investigation of STR P4 Damage Overages
    We are aware that some players are experiencing instances in Phase 4, when Darth Sion and Darth Nihilus are defeated and Darth Traya is alone, where guild members with underpowered teams are registering very large damage totals to Darth Traya. In some cases that damage is being applied to someone else in your guild.
    We attempted a potential fix last week, but it seems the problem is persisting. We have some additional fixes we will be attempting later this week and next to hopefully correct the problem. More than anything, we want you to know we are aware of the issue and trying to find a solution. It has turned out to be a particularly slippery bug. Many thanks to those in the community who have helped us to debug it by providing logs, screenshots, information, and live feedback.
    I need a new message here. https://discord.gg/AmStGTH
  • Kyno
    32087 posts Moderator
    Options
    TVF wrote: »
    https://forums.galaxy-of-heroes.starwars.ea.com/discussion/167687/content-update-4-25-2018
    Ongoing Investigation of STR P4 Damage Overages
    We are aware that some players are experiencing instances in Phase 4, when Darth Sion and Darth Nihilus are defeated and Darth Traya is alone, where guild members with underpowered teams are registering very large damage totals to Darth Traya. In some cases that damage is being applied to someone else in your guild.
    We attempted a potential fix last week, but it seems the problem is persisting. We have some additional fixes we will be attempting later this week and next to hopefully correct the problem. More than anything, we want you to know we are aware of the issue and trying to find a solution. It has turned out to be a particularly slippery bug. Many thanks to those in the community who have helped us to debug it by providing logs, screenshots, information, and live feedback.

    Just the last update we got.
This discussion has been closed.