JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by Rye Mouse: 6/26/2023 12:10:24 AM
9

PvE/ALL Content Unplayable ATM due to "Contacting D2 Servers"

As title says. Was trying to run a Last Wish raid and it was comical how many times one or two or ALL of us would be reconnected or just kicked or sent to A SERVER QUEUE. Tried to do Deep Dives only to receive countless error codes like Bee and Monkey. Bungie, I know that saying to "FiX yOuR gAmE" is easier said then done, but right now, the game is actually treading the point of being really hard to actually 'play'. :/ EDIT: Hearing about how people are experiencing Cabbage, Coconut, Weasel, and Plum errors, and I can only assume there are more that I haven't seen people experience. It's getting to the point where no matter what error code I get, I feel so numb to it, because although almost every error code will tell you "It's your connection" or so on, I know that its rarely to never on my end. Please Bungie, SOMETHING has to be done about this literal patchwork going on behind the scenes of the code... EDIT 2: Wow once again here we are, unplayable completely. Bungie, it is so hard to sit here and defend you over and over when you have now shown little to no care for the community you have cultivated. Your cash-cow of a game is falling apart, but because the temptation of people still buying into Destiny is the #1 priority, the game barely gets any server wide issues fixed. Take the game down for a WEEK for all I care, just... be open and honest with us. If the servers need a change, then do it. Stop removing 'contacting d2 servers' from peoples titles like mine and address the issue :/

Posting in language:

 

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

  • I’ve been getting “contacting destiny servers” almost every day for the past 4-5 months but I’ve only actually been booted 2-3 times in total.

    Posting in language:

     

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

  • Edited by Tech Noir Soldier: 6/9/2023 6:12:45 AM
    I love destiny but the fact is its broken atm. Bungie need to fix it asap, or do something drastic. Id stop playing for a week if they could sort some servers out or fix it once and for all. Ive had to stop playing tonight because i cant even run a lost sector with DCing twice halfway through They should offer refunds imo

    Posting in language:

     

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

  • It's tense doing a solo flawless run with Contacting every so often, it's bad enough worrying about the adds or mechanics killing you without the looming threat of the servers screwing you over

    Posting in language:

     

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

  • 1
    acbtheman
    acbtheman

    Bring it - old

    and all the bungie mods can seem to say is "it is not bungie's fault, they don't actually play on servers, it is all your own networks fault". I've seen about 4 replies like this tonight and it is frustrating as all get out to be ignored when many people are saying they are having trouble connecting to the game.

    Posting in language:

     

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

  • Contacting destiny server’s since 2014

    Posting in language:

     

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

  • It is all cause of the lousy PC players we are connecting with. They have the worst connections. Unlike the consoles that have everything streamlined for consistency. The PC community every computer is different. Since Destiny is peer to peer it screws everything up.

    Posting in language:

     

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

    9 Replies
    • PVP is getting it too. Weasel errors

      Posting in language:

       

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

    • Bump

      Posting in language:

       

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

    • I’m getting ‘coconut’ and ‘cabbage’ errors. Why do the server errors throw up different codes for different people? It makes no sense.

      Posting in language:

       

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

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