Ever since the Moments of Triumph update on June 9th the game became unplayable. Every time i log into the game i get about 5-15 currant error codes before I'm allowed into the game. Then once in the game every time I launch any activity(match made or solo) I have to launch the activity multiple times while getting currant, cabbage, cacao or even worst weasel till it lets me into said activity. Simultaneously almost every time I switch weapons/ armor or even reset an active order in the seasonal hub I get a constant spam of "Contacting Servers," followed by a 5-30 seconds delay before it actually does it.
This has made the game completely unplayable to the point that i stopped even trying to do LFG activities; nobody wants to deal with this constant spam of errors when they just want to play the game. I have put over 10k hours into this game and never had any issues playing this game with the exception of the random error codes during a launch of an expansion/ raid.
I have done and followed every single thing listed on those troubleshooting guides listed on your site. Even tried multiple different ISPs and hotspot on multiple different phones with different providers. Nothing has made any meaningful changes to the problem.
To make things worse this is the only game i have this issue in, since the update on the 9th of June I have played The Division 2(~150 hours), Warframe(~40 hours), Where Winds Meet(~30 hours) and Palworld(~30 hours) fully online with other people. Collectively between these 4 games I have experienced 2 error codes and 1 disconnect, while I can log into Destiny 2 right now and get about 50 in the first 10 minutes.
I would hope y'all can do something about this problem but I'm assuming this is just the way the game will be till the servers are shut down.
-
1 RespuestaHello there, Thank you very much for reaching out to us. I'm sorry to hear that you are running into these error codes when trying to play. While we don't have any additional troubleshooting outside of the guides you've already tried and the help articles available for the error codes, we've taken note of this thread and will continue monitoring any issues that may have gone awry from our end.