{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by YOUZA_LiL_BULLiE:
8/6/2019 3:32:32 PM
2
Bungie, You've GOT To Adjust The Parameters For Competitive Penalties
Many players don't "[b][i]quit[/i][/b]" matches, although your algorithm deems it so. All week, I played countless competitive matches. Never quit any of them so that I could receive the bonus points when reset rolls around. Even stayed in a match [b]solo[/b], and fought when all 3 of my teammates left the match early. Then, with [b]1 minute left[/b] in the match, I get error coded. There goes my bonus. Because of an error code.
- When players get disconnected, for whatever reason, your systems call it "quitting" and a penalty is enacted.
- When players are left in matches solo, they don't receive a bonus for sticking it out, they take the loss penalty either way it goes.
- When players are DDoS'd, they receive a penalty for "quitting".
- You pit solo players against stacked teams.
- You drop solo players in an already lost match, and sometimes (because this has happened to me), you take their win streak away.
Please, you've got to make some adjustments to the Crucible. I can't tell you how discouraging it was to get error coded after honoring the system and not quitting out of matches. Even if you never take a second look at how broken matchmaking actually is (although, you should), you can [b]at least[/b] take a second look at what constitutes "quitting" in competitive. Because it's just not working.
[b][u]EDIT:[/u][/b] [b]I'm not referring to suspensions. I'm only discussing the error codes received randomly during gameplay, then getting the "Oops You Left A Match" message. When you "left" at no fault of your own. Resulting in a weekly bonus loss because it was considered "quitting".[/b]
English
#destiny2
-
I agree. I had a similar issue w/Gambit. Got dropped into a losing match n lost my win streak. Weren't there supposed 2 b protections n place 4 this sort of thing? If you get a error code while playing comp, it's not quitting lol, so it should not be counted as quitting. It's these f'n P2P servers Bungie loves so much.
-
Edited by GrundleBeans: 8/6/2019 1:55:39 AMSuspensions aren't intended for quitting only, it's for leaving other players on your team at a disadvantage, regardless the cause or excuse. If manual quitting was the only trigger, then people would just quit the app, disconnect their internet, or turn off their console to get out of being punished. People who choose to quit by backing out manually aren't the only problem that suspensions try to stop. Secondly, it helps uncover players who are using an unstable connection who shouldn't be playing PvP, because every time they play, they're ruining the experience for everybody and being dropped from matches by error codes caused by their bad connections all the time is just screwing teams one after another. Yes, there are other things that should change, like reduced or eliminating point losses for players who are left to go solo against a full enemy team, etc. to make the experience better for people who deal with unfair disadvantages, but the way suspensions and restrictions are working is as intended and probably shouldn't change for several good reasons. [quote]you can at least take a second look at what constitutes "quitting" in competitive.[/quote] Suspensions are triggered automatically based on the frequency you leave matches. There simply aren't enough people to sit around manually checking [i]hundreds of thousands of people per day[/i] just to see if some of them were kicked instead of quit on their own.
