Large skill gaps make both sides unhappy
Aliases: skill gap · stomp · one-sided match · mismatched lobby
What it is
When the two sides of a match differ vastly in skill (one stomping the other), neither the winners nor the losers have a good experience. The structure of a large-skill-gap match is: the strong side wins without challenge, the weak side loses without any chance to fight back. The counterintuitive part is that this rejects "the winner should be happy"—a stomp victory provides no sense of achievement, because achievement comes from contest and a stomp has none.
Why it happens
The two sides suffer through different mechanisms. The weak side's pain is competence negation: the entire match confirms "I can do nothing here," stacking frustration, shame, and helplessness into an emotional memory tied directly to "this game makes me feel bad." The strong side's hollowness is goal absence: with no opponent, there is no skill to deploy and the match degenerates into executing a procedure—a win that proves nothing. The challenge-skill balance from flow theory explains both directions at once: optimal experience occupies a narrow band where challenge and skill match, and deviation toward either side (anxiety or boredom) degrades the experience. A stomp pushes both sides outside the band simultaneously.
Where it stops holding
The acceptable gap depends on the match's social meaning. Casual matches between friends tolerate large gaps (playing with the friend outweighs the outcome); ranked play does not (rank's fairness is the promise). The gap's impact also varies by genre: in co-op-versus-environment play, a skill gap can convert into a mentorship relation (veterans carrying newcomers); in player-versus-player it has no such conversion path. Some system designs amplify the gap's damage—when the strong side extracts outsized rewards from stomping (farming rating or economy), the system is incentivising the creation of stomp matches, a loophole matchmaking must close at the incentive-structure level.
Applying it
- Track gap metrics per match (MMR difference, score difference, duration ratio) and treat the "stomp rate" as a core match-quality indicator.
- After a stomp, adjust actively: tighten the strong side's next matching window, or tell the weak side that match protection has engaged, so the system visibly cares about the frustrated player.
- Verification: compare next-day retention across stomp-rate regimes (peak versus off-peak population). Retention's sensitivity to stomp rate decides whether off-peak waits should buy precision.