**WINTER OF WOE - BONUS OBJECTIVE POINT**
As previously announced, the team will be distributing an additional point toward milestones to anyone who completed the Absorbing Man fight in the first step of the Winter of Woe.
This point will be distributed at a later time as it requires the team to pull and analyze data.
The timeline has not been set, but work has started.
As previously announced, the team will be distributing an additional point toward milestones to anyone who completed the Absorbing Man fight in the first step of the Winter of Woe.
This point will be distributed at a later time as it requires the team to pull and analyze data.
The timeline has not been set, but work has started.
There is currently an issue where some Alliances are are unable to find a match in Alliance Wars, or are receiving Byes without getting the benefits of the Win. We will be adjusting the Season Points of the Alliances that are affected within the coming weeks, and will be working to compensate them for their missed Per War rewards as well.
Additionally, we are working to address an issue where new Members of an Alliance are unable to place Defenders for the next War after joining. We are working to address this, but it will require a future update.
Additionally, we are working to address an issue where new Members of an Alliance are unable to place Defenders for the next War after joining. We are working to address this, but it will require a future update.
Comments
This would be a possible back up plan when such bug occurs. And let's be honest, we have bugs affecting abyss almost every other month.
You are right though, you aren't the only impatient one. You are also aren't alone in those that don't understand that bug fixes are just switch you can turn on and off.
You are definitely not the only one. This bug really messed up my plans.
My champs are stuck in Abyss while this is going on. I can’t do the new event quests. I don’t have Nick Fury, Doom, or Void for important Alliance Wars.
Not to mention the units this bug has already cost, with no mention of remedying the issue.
We keep hearing that Kabam will be more transparent, things like this are a step backward.
Also don't play the transparency card. That doesn't apply here. That's just you being petty.
Best not to worry about what goes on at the top.
Most of us have the same problem here and it's very time-sensitive. Any update will be appreciated or maybe some temporary solution, that can save our resources, while the other team is fixing the bug.