Design can lower the payoff of disruption

What it is

Punishment systems handle disruption after it happens; the design layer can change its payoff structure before it happens: AFK yields no rewards, harassment finds no visible reaction, and griefing cannot convert into a match advantage. The approach of designing down the payoff of disruption replaces "punish the disruptor" with "make disruption unprofitable"—when the expected return of disruption falls below normal play, the rational reason to adopt it disappears and its scale shrinks naturally.

Why it happens

Disruption's payoff structure has multiple designable entry points. Cutting instrumental payoffs: AFK players earn no experience or match rewards (AFK detection plus reward exemption), intentional rank-droppers enter a low-quality pool (abnormal-score detection plus hidden-rating correction), and the payoff of harassing an opponent into quitting disappears (the departed player is replaced by AI or the match settles with protection). Cutting social payoffs: harassment depends on the victim's visible reaction, and muting makes the reaction invisible (the blocked party neither knows nor is affected), while spectator reporting and quick-block cut off the stage. Cutting misdirected costs: friendly fire marks the damage source rather than the injured, and interference (resource stealing, blocking paths) has system penalties aimed at the interferer. Every entry point shares one goal: make the actor bear the behaviour's cost instead of the victim.

Where it stops holding

Payoff-lowering mechanics can be weaponised in reverse: reward exemption from AFK reports invites abuse (reporting normal players to strip their rewards), so exemption decisions need an evidence threshold; block functions can be used to refuse communication in competitive play (a whole team blocking teammates' pings), so competitive contexts need a minimal communication guarantee. The mechanics' effectiveness also depends on detection accuracy, and detection error's double cost (missing disruptors, punishing normal players) shifts with the threshold—no zero-error setting exists. Payoff-structure changes also carry game-theoretic implications: players adapt to new rules and find new disruption paths (from harassment to passive cooperation, from AFK to minimal ineffective input), so payoff design is a continuous adversarial iteration, not a one-time configuration.

Applying it

• Draw a payoff-path map for each disruption type: the actor's cost, every benefit gained, and the cost borne by the victim—then design a payoff cut or cost transfer for each item.
• Reverse-audit every anti-disruption mechanism for its abuse surface: who can harm others by triggering it (malicious reporting, weaponised blocking), and add an abuse threshold to each (report credibility weighting, block caps).
• Verification: compare report rates for that disruption type, behaviour duration (from onset to stop), and victim retention before and after the mechanic ships. Shorter behaviour duration is the most direct evidence that payoff cutting works.

Related

• Same group: W9.04.1 AFK, griefing, and harassment are structural problems · W9.04.2 Report-handling speed decides community trust
• Nearby: W2.03 Challenge-skill balance · O1.03 Harassment and safety design · P1.05 Incentive structures
• Search terms: anti-griefing design · payoff structure · incentive design · friendly fire