3 weasels, 5 vipers, 3 zebras, 15 lions, 30 flies, and countless bees. That's a minor sample of my sufferance. Ok, let's be honest here. I knew I'd run into errors during the Beta. So I was OK with a few disconnects once in a while. I came into the full version expecting to see no more errors. However, I was dead wrong. Clearly, this issue has not been resolved. With such a success as Halo, I expected better when it comes to server maintenance. But I am being plagued by error codes that apparently mean nothing to you, Bungie. And I am sick of seeing that black screen with that logo in the corner that says "Screw you, sucker." And it is NOT my freaking connection that's the issue. My NAT is always open, and I use a wired connection with 0% packet loss. I frequently reset the console's cache AND my modem when I run into issues. I have heeded all of your suggestions, so don't you DARE tell me to port forward or do heaven knows what. If I don't have issues with Titanfall or BF4, then why on EARTH should I have issues with Destiny? Listen to all the other complaints about these error codes. And some REAL customer service would be nice too. A telephone line, maybe. Or more frequent responses to forum threads pertaining to error codes. Less robotic advice on attempting to fix disconnect issues. Maybe even--gasp!--admitting that YOUR servers are the problem here, not ours. Here's a suggestion: instead of worrying about content, Iron Banner, and user interface updates, you make your broken game PLAYABLE. Reduce disconnects. If someone is disconnected, attempt to reconnect them, as Titanfall did. Fix your coding. I did NOT pay $60 for a black screen, an Orbit screen, and the infamous "Noah's Ark" of error codes. And I surely won't buy any of your DLC if these dreadful issues continue. I don't care if you have to shut the servers down for a week. Get some real experts to get your connections working. Why did Halo have so few issues, while your new game has so many? I fail to understand. You're losing your market, Bungie. Others like me will not continue to play Destiny with these sporadic, unpreventable disconnects. PLEASE FIX YOUR GAME. EDIT: Lately I have been getting strictly lions, flies, and bees, in increasing order of frequency. I have dropped over 5 times in a few hours. I understand that steps can be taken user-side to reduce disconnects, but there does not seem to be a panacea for these unpredictable errors. A few things I have noticed: 1. Over 50% of the time I get KTO'd (kicked to orbit) while using my legendary Sparrow. Call it a hunch, but it seems as if the game disconnects you because it is trying to load too much data at once if you are traveling fast. I have noticed a reduction in bee errors when attempting to slow down a bit. However, this may be a placebo effect. I cannot confirm this speculation. 2. I have never been KTO'd when navigating a darkness zone solo. However, I am KTO'd from the raid and crucible extremely frequently. This seems to suggest that communications with other players ultimately cause most, if not all, disconnects. 3. Bee, fly, and lion are similar in nature: they are characterized by "general disconnections between you and the various routes your traffic takes across the internet to get to Bungie. This includes packet loss or disconnections between your home network and Bungie." Because I have a wired connection with 0% packet loss, the other possible explanations for my bee errors are disconnections with Bungie, excessive bandwidth usage by other devices, my particular Wifi setup, and faulty in-home wiring. The latter three can be eliminated since such issues would affect ALL of my games, not just one in particular. That leaves disconnections as the only plausible explanation offered by Bungie for my case. 4. Something about the wording of the error code message recently got my attention. "Removed from the game world." At first glance, this seems innocent, as if you simply lagged out of the game. Upon closer interpretation, it sounds as if you didn't lag out, but as if discrepancies with your connection caused the servers to kick you from your game. In other words, a small disturbance in your connection with Bungie will cause the servers to drop your connection, giving you a KTO. This idea makes sense since the game clearly makes no effort to reconnect you to your game (save for a few times when I have gotten the message "Contacting Destiny Servers..." I have never successfully reconnected, however). This is only theory.