{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/30/2018 7:44:00 PM
3
What about players who "quit" due to outside forces? Or have to leave just this once because they have something of importance to due in the real world? Should they also be grouped up with the people who leave losing games religiously?
Lets say you're in a game, and, for no fault of your own, your power goes out? Or your Wi-Fi dips for a moment, or any number of other things that are out of your control? Well, by your logic, you're now condemned to play against ""quilters" for the rest of your days. Hope it was worth leaving a game unfinished cause you got called into work or had an emergancy, cause your d2 competitive experience has just been decided by it.
English
-
If you have other stuff to do in real life, go to Quickplay. Other connection issues are logged with the zoo animal error codes. It is easy for Bungie to figure out who is willingly quitting and who is being dropped due to other issues.
-
So suddenly getting called into work unexpectidly, thats a punishable offence, and if you arent punishing players for connection issues, then whats stoping someone from faking a connection issue to get out of a game,slighltly moving the ethernet cord from the back of the console will give you an error code, or unplugging it all together, ect.
-
I've never been called into a job that required me to immediately drop what I was doing and run to the job. If you work as an emergency responder or something of that sort, than you understand the risks in starting anything before suddenly being called into action. Those are very special cases and do not apply to the majority of players that are playing COMPETITIVE to COMPETE for a better rank. If you have a job that requires you to drop everything at an instant, maybe you should wait until you are not ON CALL to play video games.
