{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by PitchBlackVoid:
10/28/2014 4:46:04 PM
12
Zebra replaced by weasel, problem not actually fixed
Well I was super happy to read today's patch notes and see that I shouldn't be getting the "zebra" error anymore, which would always knock me all the way back to the title screen. And I didn't! Instead, I got "weasel"! Same problem with a bright, shiny new stupid animal name! And the Help forum doesn't seem to have any info on this new rabid beast that'll continue to ruin my Destiny experience.
For any tech folks from Bungie that are reading this, I'm getting the error pretty consistently at the 2 minute mark (or close to it) whenever I start any activity in Destiny. Tower, patrols, story, strike, crucible, doesn't matter. This has been an ongoing problem for the past couple weeks, with exception of the [i]occasional[/i] hour or so of error-free play. But that's followed by more errors.
I really like Destiny, and I'd love to play it with no issues like (apparently) the majority can.
I has a sad.
Gamertag: xHOBOxCOREx
Console: Xbox360
-
I have a come to a stunning conclusion. The Servitors in the game are the same thing as Bungie's Servers: Whenever a 'solution' is fed into them, they explode. Coincidentally, 'Server' is also a code-name for Animal Zoo. On a related note: I feel your pain, i have an entire African Safari living inside of my Xbox 360 when i boot up Destiny
