What you need to know
- For the last week clans haven't been earning clan XP towards project completion and rewards.
- Today's regular weekly server maintenance should provide a fix.
- Global Event Reanimation also starts today.
The regular weekly server maintenance is happening again in The Division 2 and this week a pretty annoying bug, at least for clans, should be getting fixed. This pas week clans haven't been generating clan XP as they play through the game, which means no clan project completion and no progress towards reward caches.
The fix is obviously welcome, but there's no word on whether clans will be reimbursed in any way for the last week's loss of XP in any way. But at least from today everyone should be back to normal however frustrating it is.
Also starting today when the servers come back up is the latest Global Event Reanimated. As usual it's an opt-in event with a bunch of rewards on offer right up to the Headhunter backpack charm for completing all the challenges. If you're not taking part in the Global Event and go into matchmaking, you'll be matched with other players also not taking part.
It's also the second week of the Huntsman League, so if you've still got some stages to complete there you've got another seven days to crank them out and get all the rewards.
Maintenance began at 09.30 CEST (03.30 Eastern) with an estimated three hour downtime.
Happy hunting, agents.
The Division 2: Warlords of New York brings a pack new expansion, with story missions that will see players hunting down the rogue agent Aaron Keener.
Richard Devine is an Editor at Windows Central. A former Project Manager and long-term tech addict, he joined Mobile Nations in 2011 and has been found on Android Central and iMore as well as Windows Central. Currently you'll find him covering all manner of PC hardware and gaming, and you can follow him on Twitter and Instagram.
Get the best of Windows Central in in your inbox, every day!
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.