Forced logouts need advance warning, not mid-match interruption

What it is

Forced logout ends a session when the playtime cap is reached, mostly as a statutory anti-addiction requirement for minors. Its execution quality decides the experience: abruptly cutting a match in progress (a teammate missing, ranked points penalised, progress lost) shifts the protection mechanism's cost onto players and teammates, while advance warning—clearly announcing remaining time and a suggested wrap-up point as the cap approaches, letting players end at a match boundary—minimises the same rule's experiential harm.

Why it happens

Warning's value is converting "external compulsion" into "informed arrangement." An unwarned forced logout happens outside the player's perception (immersed, unaware time is up), striking a moment with active goals and dependencies (a team mid-match, unsaved progress); the lost experience is loss of control, and player resentment concentrates on that moment. Warning gives a control window: a player who knows "the match ends, then I'm out" adjusts behaviour (no new queues, wrap up in the current match), and the interruption point shifts from "the system's arbitrary moment" to "the player's chosen moment." Technically, warning requires linkage with the match system: detecting whether a match is in progress (deferring logout to match end, or warning early enough that no new match starts), a computable countdown (not a vague "logging out soon"), and a clear post-logout state (tomorrow's available hours, progress saved).

Where it stops holding

"Do not interrupt matches" and "enforce strictly" are in tension: if the statutory limit's enforcement point is hard (offline at the minute), deferring for matches lets total time exceed the cap, and the precision-versus-experience trade-off follows the regulation's flexibility space—most regulations enforce "time-window limits" (minors' playable hours), and match handling at window boundaries (matches started before the boundary may finish) is common compliant flexibility. Warning lead time is a design parameter: too short (5 minutes) cannot finish a match, too long (1 hour) leaves the player in a half-experience of "waiting to be logged out," and 20-30 minutes matches a standard match's length. For competitive player groups, the teammate-gap problem of forced logout needs system-level mitigation (ranked-queue restrictions before logout, AI takeover, or match voiding), moving the protection mechanism's cost off teammates.

Applying it

• Start showing a countdown at 80% of the time cap ("20 minutes remaining"), and when the player queues a new match, clearly warn "this match may not be completable."
• Defer mid-match forced logout until match settlement, or apply AI takeover / match voiding after logout, so teammates never bear the gap.
• Verification: track the share of forced logouts occurring mid-match and the correlation with negative reviews or support contacts before and after warning design. A falling mid-match share with fewer complaints means the warning is achieving its design goal.

Related

• Same group: W10.07.1 Playtime reminders must be proactive at key thresholds · W10.07.3 Anti-addiction's real effect depends on account and device identification accuracy · W10.07.4 Crude time-management tools breed circumvention rather than less play
• Nearby: W10.06 Minor protection and real-name systems · I1.01 Session length and entry cost · W9.01 Matchmaking and balance
• Search terms: forced logout · session cap · graceful interruption · anti-addiction system