This is going to be brief. Error codes that I'm seeing everywhere include CABBAGE, LETTUCE, RABBIT, QUAIL, URCHIN (in normal Zero Hour at the end of the activity), HONEYDEW (Forsaken be Forsaken) and CURRANT (I don't know a single friend who does not get this error). This game is the only thing messing up. Other devices work fine, other games work fine. The rate of error codes occurring tends to change after each UPDATE/PATCH, NOT after MAINTENANCES (keep that in mind). I don't even think it's a connection issue. As always, I'm pretty sure it's some sort of loading glitch, because those are VERY apparent in the game right now ("Placeholder Type" text with pink imagery appearing over icons on the map and flashy effects everywhere in the UI). And there is no "Contacting Destiny 2 Servers" message. A lot of these codes happen when you start traveling to another destination, at the start of an activity or after someone hits a loading zone. Each one of these errors kick you to Orbit. Should this not be a priority when the Bungie team gets back to work on the game after the break? Because new content isn't going to matter if the game just stops working. ---------- Also, new issues are rising with the new content. I've witnessed the Tower Obelisk bugging where you can't interact with it, just like the EDZ Obelisk. Also in the Sundial, if you are dead for too long after the Psion boss is defeated and everyone is already teleported, you can get stuck outside of the Sundial and be unable to claim your rewards. I've witnessed a friend have that happen to them. I hope these issues get resolved after the game gets a little more stable. EDIT: Also, my old post about CABBAGE and LETTUCE is getting attention once again in the Help Forums. Doubt it's a coincidence.