**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.
Stack Overflow Global Node Not Functioning
Havic000
Posts: 1 ★
Same as title. Tried a full team of tech champions and neither Sentinel’s incinerates nor Sparky’s shocks had any sort of increased duration. I also tested IMIW’s shock and incinerate debuffs and they had no noticeable duration increase. Furthermore it notes all debuffs so this should have extended to parry stuns and all other non damaging debuffs such as sentinels armor breaks and heal blocks. This was done with a team of 5 tech champions so it should have resulted in 40% increased debuff durations.
1
Comments
We are looking into an issue with the Stack Overflow node right now.