Wednesday 4 October 2017

Destiny 2: Servers are gone down for maintenance

Destiny 2 players should discover something else to possess a couple of hours of their chance today, October 3, as Bungie has taken Destiny 2's servers disconnected for scheduled maintenance. This will be trailed by the release of another hotfix update and the kickoff of Victory Week, which caps off the current Faction Rallies event. [Update: Servers are currently back online in front of schedule; hotfix update 1.0.3.1 is live and a Faction Rallies champ has been reported. In case you're experiencing difficulty signing in, Bungie recommends closing and re-opening the game.]

Destiny 2 Game Cover Image
Maintenance started at 8 AM PT/11 AM ET/4 PM BST/1 AM AEST, and soon thereafter players were prevented from signing in. Those effectively online at the time can keep playing, yet everybody will be booted disconnected at 9 AM PT, regardless of what you're doing. As it were, it's not a perfect time to attempt this week's Savathun's Song Nightfall Strike. 

Bungie's schedule calls for maintenance to end at 12 PM PT/3 PM ET/8 PM BST/5 AM AEST. Nonetheless, we've seen various maintenance periods as of late last for longer than anticipated, so you might need to be set up to hold up until some other time than that before you're ready to play. We'll report back with any developments.

Destiny 2's weekly reset has just happened, presenting new weekly Milestones and the previously mentioned Nightfall. Nonetheless, Victory Week doesn't authoritatively start until after maintenance is closed and hotfix update 1.0.3.1 has been released.

By then, Bungie will declare which of the three factions rose victorious from the weeklong Faction Rallies event. The triumphant faction will then offer its special weapon available to be purchased - players can purchase it for 50,000 gleam, or 1,000 on the off chance that they were an individual from that faction. This will be accessible for one week, amid which time you can cash in any Faction Tokens you may still have in your stock.
Previous Post
Next Post

post written by:

0 comments: