Punishment must distinguish deliberate quitting from network failure

What it is

Intent-sensitive quit penalties use behavioural evidence to separate "close the client to escape a loss" and "repeatedly go idle" from broadband outage, system update, or an emergency. The goal is not zero punishment; it is correspondence among responsibility, loss, and changeable behaviour.

Why it happens

Network failure has detectable shapes: the client vanishes without preceding failed decisions, a platform network event occurs, multiple matches drop in one period, a reconnect is requested, and no input sequence completes. Deliberate quitting often shows the reverse: closing immediately at a loss, refusing reconnection, repeatedly abandoning disadvantage, then entering another game. The system should first allow low-intensity recovery—pause, leave-room option, reconnect window, and proxy control—and reserve punishment for repeated absence without recovery attempts. Grading needs rhythm: first reminder, temporary low-commitment modes only, then ranked cooldown later, rather than an immediate permanent ban. The notice should state evidence category, impact, duration, and restoration conditions.

Where it stops holding

Evidence is uncertain: a router can fail right after a loss; a parent unplugging, dead battery, or update may be invisible. So a single disconnect cannot be judged deliberate, and appeal cannot be the only remedy. Modes carry different risk: casual and practice play may use low or no penalties, while ranked and league play enforce stricter commitments; players must be able to choose a mode matching their network reliability. Mobile devices, shared networks, and sudden caregiving need emergency pause rather than moral judgement. Abuse detection must also prevent reverse gaming—manufacturing a few "real" failures to build an innocent record before quitting.

Applying it

• Compute reliability from session and network signals: consecutive disconnects, reconnect success, timing of active closes, platform events, and appeal history; apply different thresholds by rank and mode.
• Give first or explainable absences a reminder and recovery task, and apply temporary restrictions to repeated absence without recovery; explain evidence category, duration, and removal conditions in the notice.
• Verification: compare deliberate quits, wrongful-punishment appeals, return rate, and queue times for normal network players before and after penalties; sample successful appeals and feed them back into detection rules.

Related

• Same group: W9.10.1 Disconnection harms other players · W9.10.2 Reconnection and proxy control are needed
• Nearby: O2.02 Appeals and transparency mechanisms · W9.05 Reporting, blocking, and punishment · K1.02 Latency and network resilience
• Search terms: quit penalty · leaver buster · rage quit detection · fair enforcement