It’s been common knowledge for as long as MCC’s been around that errors in the various games’ netcode cause players to be booted to the main menu. It’s gotten a lot better over the years, but since quit bans have been ramped up, there is a more pressing issue: MCC still can’t tell the difference between when a player is kicked due to an MCC crash and when the player quits.
Players should not be penalized for MCC’s errors. Sure, ideally these crashes would happen so rarely that the point would be moot, but that’s not the case. I rarely have a CE play session where there isn’t at least one crash. When these issues happen, MCC needs to be smart enough to know it was an issue on their side and not give the player temporary bans.
I don’t think there’s a way for a system to differentiate crashing from just closing the game.
If the MCC didn’t penalize you for crashes PC players would manually crash the game when they would like to quit to avoid the quit ban. I think the better solution is to solve these stupid crashes that happen in H3 and CE.
> 2717573882290912;3:
> If the MCC didn’t penalize you for crashes PC players would manually crash the game when they would like to quit to avoid the quit ban. I think the better solution is to solve these stupid crashes that happen in H3 and CE.
If these crashes are taking place on the client, then I agree. But if they’re something that is caused (or at least detectable) on the server side, then 343 needs to differentiate.
> 2717573882290912;3:
> If the MCC didn’t penalize you for crashes PC players would manually crash the game when they would like to quit to avoid the quit ban. I think the better solution is to solve these stupid crashes that happen in H3 and CE.
Console players can do it just as well…
I don’t use skins but I like to see other players skins and armor combinations. Unfortunately, I’ve had to turn off all new content because my game will crash (turning off my Xbox as well) frequently