Game Crashes Should Not Impact CSR

I know this is a difficult one to figure out, but there is really no excuse for losing ranked credit because the game is broken.

Its absurd, and its not fair to the player it happens to, and in the case of team modes its not fair to the team that lost a player because of it.

I just had my game crash in Ranked FFA because two people threw frag grenades at me at the same time. No exaggeration, that’s the cause of it. The same thing happens when a Wraith shoots me in BTB or something. Guess how often people spam grenades in Ranked FFA.

I’m going to lose 15 CSR which at this point amounts to two first place wins, and its not my fault in the slightest. I crashed earlier in a social game so I probably should have just deleted the game entirely by this point.

So how am I incentivized to keep playing when this is a thing that still happens?

2 Likes

I know that it’s hard for them to tell the difference from their end in regards to a quit vs a genuine crash.

But you would think they could use AI to work some of it out; using error codes generated by the game or machine, the pattern of “crashes”, the frequency.

Lots of “crashes” on certain maps or game types is suspicious. Especially early in the game.

Only crashing when you are behind on the scoreboard is very suspicious.

So you think they could cut every player a little bit of slack. Then come down hard if they are shown to be repeat offenders.

And that’s before we even start with the ludicrous lack of a rejoin feature.

2 Likes

I mean, I just went 22/14/7, got 2nd place, and only got about 3 CSR. Its impossible to come back from a game crash. I get less than 3rd place and I lose CSR, and winning is very difficult when the main strategy of playing FFA is the actual opposite of how you should play every other Halo mode so I can’t bring myself down to that morally bankrupt level.

I knew better than to even try with this garbage.