Avatar

THAB 10-04-2018 (Destiny)

by DiscipleN2k @, Edmond, OK, Thursday, October 04, 2018, 21:18 (2081 days ago) @ CruelLEGACEY

They are bringing back quitter penalties (although increasing the number of games you must leave to incur such penalties). No mention of people quitting to screw the other team out of the Malfeasance boss kill.


This is something I've never understood. Why can't the game just lock the quitter out of whatever activity they left (or maybe even lock them out of any activity with matchmaking) for the average length of time it takes to complete that activity. Throw a fit and rage quit because your team is getting steamrolled in Crucible? Take 12 minutes to cool off, but you don't get to start a new game while your old team suffers. Have an exploding diaper emergency in the middle of your strike? Life happens. You're locked out for 15 minutes, but that will probably be over by the time you're back anyway.


I think that the problem has historically been that they’ve had trouble separating “quitting” from network failures or other random disconnects. They don’t want to be too strict on quitter penalties because they’ll also be applied to people who are booted through no fault of their own.

I don't know how they wouldn't be able to see that a player went through the steps necessary to manually leave an activity. In fact, I'm pretty sure that when you're in a guided raid, the system warns you about a quitting penalty if you start to leave. I think at some point Bungie even specifically said they could tell the difference between quitting and network issues, but I could very well be confusing that with them talking about cheating via network manipulation vs legit network issues. They even have that thing that tries to automatically drop you back into strikes or raids when you disconnect that doesn't happen when you quit and start a new game, so it seems it's at least pretty good at knowing when you disconnect and when you quit.

That said, if there is still a good chance of some false positives when identifying quitters, I'd definitely rather deal with a few whiny-baby a-holes leaving my team short-handed than accidentally punish people with crappy network issues.

-Disciple


Complete thread:

 RSS Feed of thread