If my ancient laptop knows when Word or Excel is crashing or not responding, why can’t they program the Series X to recognise when MCC is crashing?
Why does it automatically assume I’ve quit the game and ban me?
I don’t understand why it cannot detect the difference between a crash and a quit/shutdown.
I’ve switched off for the evening as this is yoink
Report this https://support.halowaypoint.com/hc/en-us/requests/new
It makes sense to not discriminate between system crashes and straight up quitting a game, as it’s very difficult to tell between the two. The same goes for network drops. How does the game know you haven’t just unplugged your router? If it allowed for network drops, you could just turn off the system wifi mid-match and get away scott-free.
HOWEVER, this should only be a feature in ranked/competitive matches. Having a leaver ban in social games is not doing the experience any favours, and serves only to make the game more boring for people who are getting stomped by a 4-stack of veteran players. 343i don’t care about that though, as they’ve got more important cosmetic pieces to make, and have to divert a lot of resources to the dumpster fire that is Infinite.
Disagree. Any system like this should extend to social matchmaking, but only when determined via long term trends.
If you quit once a day for a couple of days, no big deal.
If you quit multiple times a day for a couple of weeks/months, now these should become actionable in some way.
Here’s how you fix this:
Don’t dish out a punishment until the match is over & give a leeway if it happens close to the match end. If someone abuses this leave it to player reporting to find the antagonistic players.
Oh & allow people to rejoin a match at any time or have to physically opt out of that match before they can matchmake for others.
Just had a crash on my pc for the first time…
That’s just it though, why can it not recognise the difference between the game crashing and someone just force closing the game or pulling the Ethernet cord out? You say it’s very difficult to tell between the two but I’m not so sure, hence my post.
I believe my Series X recognises the crash because after a while it closes the game and returns to dashboard. I think the difficulty is in getting the series x which has just detected the crash to link up with the MCC game server to pass this information on.
Perhaps this is too difficult for 343 to implement, but it would be great if it could.
The ban is very unjust when it’s due to a crash, and technically the fault lies with the 343 programming and/or Microsoft operating system rather the gamer.
If you’re on a Xbox have secondary accounts for when the system screws you. Bans mean nothing when you swap to a Smurf take the power away from the ban system. This is the solution until they add a way to see if a quit is a quit or if it’s a crash
This only works when the other matchmaking features are actually executed properly.
The team balancing is all out of whack, and you aren’t allowed to select anything that allows you to not match against parties. This is the crux of the issue in socials, because people don’t enjoy being stomped. I sure as hell don’t, and I (like almost everyone else) don’t want to be punished for leaving a match that is clearly unfair and unfun. A lot of the time, its a significant portion of matches that are one-sided (both in favour of your team, and the other), which means people are gonna leave a match far more than once a day, if they want the small chance of finding a balanced lobby.
If they balanced the teams better, and allowed for non-party matchup toggle, this suggestion would actually be viable. But at the minute, the issues stated would prevent this from being effective. You could scale the parameters for ‘excessive leave count’ to offset this, but you’d end up with a system that would allow hundreds of match leaves per week, in which case you might aswell just not have it, as anyone leaving 100 matches a week is probably a grief-bot.