**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.
Opening a 2nd (or 3rd) battle group in alliance quests
BKSwisherSweet
Posts: 136 ★★
Is something only officers should be allowed to do. Our alliance starts every week with map 5 for just one battle group to gain prestige by completing it, but every time someone will open a second battle group even though in alliance chat we tell everybody not to. If only officers were allowed to start 2nd and 3rd battle groups this wouldn't be as much of a problem since you can demote officers.
Is this a problem for other alliances?
Can we fix this?
Is this a problem for other alliances?
Can we fix this?
1
Comments
This is just an alternative solution in case Kabam doesn't change it.
Guess, I know it now.