**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.
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.

Why is the no Compensation when Emergency Maintenance happens?

EbbtideEbbtide Posts: 292 ★★
I'm playing through the Halls of Healing now, but won't finish due to Emergency Maintenance. Any others doing the same will also miss out on the rewards here. The same is true to fighters in the middle of Alliance Quests and Alliance War fights, as they will lose out on health and time. Players in Arena will miss out on points and the fighter they are in will need to be "helped" to come back to fight in time.

Why aren't heals, revives, refreshes and boosts issued out when the game goes down to make up for lost time and dropped fights? The game used to do this with the Lofty Standards message, but hasn't done this in months and I'm not sure why.

Comments

  • MidnightfoxMidnightfox Posts: 1,070 ★★★
    Nothing like pre maintenance maintenance. Starting to expect it now.
  • Hey there,

    We don't discuss or ever start looking into these kinds of things until we are sure that the issue has been solved, and that it won't happen again. Only then can we be sure of the impact it had on Summoners.

    We're really sorry that this occurred, and we're currently looking into getting it solved as soon as possible.
This discussion has been closed.