Destiny 2 Known Issues List Updated Including Event Vendor Glitch

​

Other known issues also include the CABBAGE error codes that players have been reported that caused them to be blocked from the main Destiny 2 campaign. Clearly a huge issue considering that the bulk of gameplay within the Bungie shooter can't even be unlocked until the final mission is completed.

That same error code has also affected how players can return to orbit after certain activities. The amount of errors have been reduced through troubleshooting, but they are still actively working to completely resolve the problem.

A few other issues are being looked into in preparation for the next scheduled maintenance period, including fireteam errors, loot drops, and vendor availability. The full list of active investigations, courtesy of Bungie, can be seen below:

​

Destiny Hotfix 1.0.3.1

On Tuesday, maintenance was conducted to support the deployment of Hotfix 1.0.3.1 to Destiny 2. Upon conclusion, there was a minor issue where some players were prompted to create new characters in an alternate service environment. No characters or items were deleted due to this issue. For resolution, closing Destiny 2 and relaunching the application would return characters to their proper state.

Event Vendors: Availability Issue

On September 26, Faction Rally vendors were not available in some Tower instances immediately upon the weekly reset. We are investigating the cause of this issue, as well as potential ways to address it. Similarly, Lord Saladin is expected to be impacted when Iron Banner becomes available on October 10. If you are unable to locate Saladin within your Tower after the weekly reset, we advise returning to orbit and launching into a new Tower instance.

Destiny 2 Error Code Investigations

At this time, we continue to investigate reports of CABBAGE errors that are blocking some players from progressing through the Destiny 2 campaign or returning players to orbit from alternate activities.

Some players have been able to reduce the frequency of these errors by following recently updated troubleshooting steps listed in the help article linked above. Some steps listed may need to be taken by an internet service provider to adjust security restrictions on network hardware. We will provide updates on this investigation when available.

Additionally, we are investigating elevated levels Newt, Beaver, Guitar, and Permissions errors impacting Destiny 2 gameplay. If you encounter these issues during gameplay, please post a report to the #Help forum detailing the following:

• Were you in a Fireteam when this error occurred?
• What was the activity that you were engaged in when experiencing this error?
• Have you followed steps within the Network Troubleshooting guide to ensure proper network configuration for Destiny 2 gameplay?

Have an issue you would like to report? You can join the forum to help make Destiny 2 a better experience right here.