Us middle east players bought the game excited for final shape to play with friends grind with them then final shape dropped introduced cabbage errors. We thought Bungie would fix it; they said it on Twitter that it was getting resolved, but one side of the region didn't, which is the middle east. Bungie somehow blocked us from their servers with results that continuously gave us cabbage error codes, sometimes quail or rabbit. With the recent maintenance, the majority of my friends experience has gone even worse. Now they cant do any activities without getting an error code and are ready to quit the game. Bungie is here blaming our routers when I can guarantee that the final shape launch maintenance did something on the on the middle east side of the servers, which resulted in blocking access to destiny servers with cabbage.
This is to bungie double check with the ISP; they did not do anything when final shape launched. Our routers have UnPn enabled by default. I personally did port forwarding in the game; it literally shows NAT OPEN yet still cabbage, and this is happening to many Middle Eastern players.
Bungie needs to investigate thoroughly and address any server-side issues that may have arisen during the “Final Shape” launch
-
4 RepliesHi there, Thanks for reaching out! These errors typically signify you’re encountering a broad networking problem. We recommend you refer to our Network Troubleshooting Guide to explore potential solutions to your problem: https://help.bungie.net/hc/en-us/articles/360049496531-Network-Troubleshooting-Guide