JavaScript is required to use Bungie.net

Help

Help us help you.
7/13/2019 11:29:45 PM
24

Pardon our Dust

Checking Twitter and on the website and I don’t see maintenance going on so why am I getting disconnected from matches with “pardon our dust” I’m really frustrated with the fact that this is an ongoing problem: invisible people in crucible, unbearable long loading instances in strikes that you can’t progress, being kicked from matches and being penalized. These are all much more of a priority than getting the stuff in September ready. I don’t care if we have to wait til December for ShadowKeep, make sure the games working properly BEFORE HAND
English
#Help #gameplay

Posting in language:

 

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

View Entire Topic
  • Long post. Tl;Dr - Competitive everything is in the worst position right now because of the penalties associated with all of these bugs (AND with these exploits people are abusing to get Glory/Infamy), and it's making actual quest-lines almost impossible to complete. This has been really bothersome. I initially didn't want to attempt the Mountaintop quest -at all- because the triumph seemed nigh impossible to complete on my own. It's been pretty slow since getting my characters to where I want them to be, and I'm not a raider, so I decided to give it a go. I did the same thing last season, and ground my way to Luna's and Recluse "solo," so I figured, "Why not?" The triumph was hellish, as I'm sure everyone who tried, failed, or succeeded knows already, and the double kills took five-ever in Mayhem, with me averaging around 1-2% a match, -if that-, but I did it. Finally. All that's left is to grind to Fabled, which, for me, was not so bad last season, so much so that I never needed a set group. Happy times. Great. I got to about 1100 in a few hrs of play. I was feeling pretty good. I played -just one more match-, because "Why tf not?", and I was sent to spectator for 3 straight games in Countdown. We had to try to win 5 in a row to steal the victory, and obviously we didn't. I was pissed, but I just thought it was a fluke. Next game: some trash bears being trash decided to do that exploit people are doing with matchmaking, where one team leaves in the beginning and then the other team wins by default--problem is I was not in their little crew, so it ends up being 1 v 4. If I leave? I get penalized, maybe suspended. If I stay? I have to wade through six rounds of being killed for no reason and still lose points. I leave because it's stupid that this is even an exploit at all, that there is a whole website for it, and that Bungie seems to not care about reporting players at all. I try -one more time- and we're straight for 6 rounds of countdown. Feels ok, we're tied 3-3. Some dude on my team is forced into spectator mode (I had to deduce this because he came back 2 rounds later), and it screws us out of one round completely, and we have to eek out the next one with a good super from me. He comes back and it's 5-4, so we're up. BUT GUESS WHAT HAPPENS? He's sent out again, and we lose the next 2. By that point, I'm just done. Done, done done. Unplayable. Either the other team is exploiting or the game is handicapping my team, and on top of it, I/we are getting penalized by losing points or, worse, getting banned for it. And I'm/we're supposed to get Fabled to get this quest done under these conditions? Just needed to vent. I'm so sick of this. To those of you exploiting PvP by the way: rot. Lag-spiking, or using the matchmaking exploit (https://www.reddit.com/r/destiny2/comments/a1euwi/comp_exploit_everyone_should_know_this/) trash. Trash trash trash. The game is already broken, obviously, but this just ruins it for everyone else.

    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