{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/11/2014 5:10:09 PM
4
Beta fine.
Day one fine.
Day two............ 80% failure rate due to error code: bee. Mostly multiplayer but it expanded into story, patrol, and visits to the tower. Occasionally error occurred right before the end reward screen. This marked it as completed but skipped loot...
This is the same game system and network that can play FF14 beautifully.
End result: Rage Quit
English
-
I am exactly the same as your post!
-
Same thing has happened to me bro. Not a single problem other than when Bungie was testing during the alpha and beta. Day one was perfect aside from the PST wait, and then day two blam! Can't even complete a story mission or visit the tower without getting kicked and getting error code: bee. PS4 wired connection ports forwarded upnp, even tried direct connect to the internet. Still got error code bee. This SUUUUUCCCKKKKSSS!
-
Thought it might be better today. 2 story missions down, 2 pvp matches down, and a bit of patrol, all good. Then I get bee in the last minutes of a pvp match. Notice issues with server connection while at the tower. And get kicked out of the "boss" fight for the intro mission of a new character. Is this a joke? Bungie's doing a great job of raising my hopes only to smash apart them like a Titan's super. The least they could do is make a formal statement acknowledging the issue. All they do is direct you to a page for the error and tell you they've been informed. Maybe I've been coddled but I'm used to companies informing their players about issues people are having with their game. As it is, I have yet to see anyone outside of forums talk about these errors.
-
Yeah, this is getting me close to full on ragequit. I've had the best games of my life be shattered by error code: bee and Bungie won't even address it!
