The long -awaited expansion "Final form" for Destiny 2 it has already come out. However, the event, which had every chance of becoming a holiday for fans, eventually brought only a negative. Due to serious problems with servers, some of the gamers simply could not enjoy the game.
The Final Shape should complete the story arch, which stretches from the first Destiny . This aroused genuine interest to the audience, thanks to which the peak online in Steam reached the mark of 314,634 people – his own record of 316,750 people Destiny 2 I couldn’t beat. It is possible that this was prevented by the troubles with the servers.
After the complement exit, users Nonukcasinosites.co.uk/review/hello-fortune-casino/ could not connect to the game, and if the connection was still installed, then the system threw gamers from the campaign levels, missed important KAT scenes and did not count progress. As a result, upset players spilled their anger not only in posts with complaints, but also in the section with the project estimates. In the same Steam rating "Final form" measured in the "red" region – only 39 % of positive reviews. “It seems that in three additional polishing months the developers have not bothering to check, Whether they can stand it their servers release additions ", – wrote one of the dissatisfied.
Bungie responded to the situation, apologized to the community and gave some advice to those who were faced with technical problems in The Final Shape. For example, to see the missed screensavers, the team proposed to outplay the corresponding missions.
We ask for forgiveness if the connection problems did not allow you to play in addition today. We created The Final Shape as an exciting adventure with an emphasis on the plot that will cause a surge of emotions and everyone will like. We really are very sorry if the problems with servers and stability prevented you from enjoying the gameplay. We promise to work without turning hands until the mistakes are fixed.
From the appeal Bungie
The team really managed to fix several problems. For example, the recent restart of servers improved the situation with various kinds of errors with code names Currant, HoneyDew, Weasel and Plum.
