JavaScript is required to use Bungie.net

Forums

originally posted in: Eel and anteater error codes
1/23/2015 7:57:22 AM
2
You are not alone, on x360 anteater and his friends, and also assload of baboon errors. They screwed something in the "no cheese" patch but they are too ashamed to admit it.
English

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • look i have a ps3 and im having the same problems and its so frustrating because i played beta and it DIDNT have this problem until Liizard a group of hackers in the U.K. started messing with destiny on both systems trying to hack it backwards to be a cross console game the group was caught but bungie is still trying to undo what they have done or they are getting Lazy.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • I don't think it's a matter of shame or trying to hide anything, it's a huge game and must be an absolute nightmare Jenga tower of code to keep stable with so much going on. And it's very easy to let something like this inflate to seem like a much bigger problem or even insult when you're actually just the unlucky one out of millions. My frustration comes mainly from the lack of information about what this problem is. Eel has been the most common error this week, but 'general networking problem' doesn't tell me anything and I'm really not seeing many instances of people hitting it, so it has me worrying that it's something on my end. I'd really just like to know whether I can be trying to solve it, or at least that Bungie are seeing enough instances to need to work on a fix.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon