With the Destiny 2 beta days away, Bungie has outlined a number of issues players may run into.
The developer said that this has to do with it being a beta build, which is to be expected. Some of the problems may interrupt gameplay, whether due to server instability or other bugs.
The biggest and most obvious one is networking issues, something you’re bound to run into in a stress test like this.
Other issues include location names not appearing in Crucible matches, bugs related to joining an in-progress game of the Inverted Spire strike, missing localisation for some content, and more.
Here’s the full list as of the time of writing:
Players may experience a variety of networking error codes when attempting to play the beta
Bungie will be testing server stability throughout the beta, which may cause error codes to appear periodically
Location names sometimes do not appear during Crucible gameplay
Players sometimes are kicked to orbit after witnessing a black screen when entering a Countdown match
Players may sometimes be placed at the beginning of the Inverted Spire strike when joining in progress
Sandbox balancing is still taking place: some weapons or abilities may have higher or lower damage than intended
Not all content has been localised in all languages
If you encounter any network related issues during the Destiny 2 beta, please follow our network troubleshooting guide to ensure proper network settings for Destiny gameplay
Bungie suggested that players report any issues not listed above in the help forumif and when they run into any.
The Destiny 2 beta starts first on July 18 for pre-order customers on PS4, then a day later on Xbox One. It goes open to everyone on July 21. The beta includes access to a single-player mission, a strike, and two PvP maps and modes.