anchor

Use when

Designing a low-skill-floor game that feels ecstatic through reward scheduling and disproportionate feedback on a single simple action.

Peggle

What it is. A pachinko-like arcade game: aim a launcher at the top of the screen, drop one ball, and watch it ricochet through a field of pegs, lighting them up. Clear the orange pegs to win the level. The input is a single angle; the payoff is a cascade.

Player fantasy / why it’s fun. I barely did anything and something wonderful happened. The pull is maximal juice on minimal input: you set one angle, and the game rewards you with an escalating fireworks show — lucky bounces, a “free ball” bucket, and a final slow-mo, orchestral, rainbow-explosion victory that’s wildly out of proportion to the click that caused it.

Design DNA

Take a trustworthy physics sandbox and lay a variable-ratio reward schedule over it, then celebrate every outcome — especially the lucky ones — with disproportionate feedback. The skill floor is near zero (aim and drop), but the feel is ecstatic because the physics manufactures surprise and the juice amplifies it. The genius is the gap between input effort and output spectacle: a single trivial action detonates a chain of delightful consequences you didn’t fully control but feel credit for.

The design does two clever things at once. First, it outsources complexity to physics — the player supplies one number (the angle), and the peg field plus deterministic bounces generate all the richness, so the game is deep without the input being hard. Second, it launders luck into feeling like skill: because you chose the shot, a lucky twelve-peg cascade reads as your triumph, not the RNG’s gift. The variable-ratio schedule supplies the surprise; the aim supplies the ownership; together they make a near-zero-skill action feel earned.

The hidden design work is honest physics — swept collision so the ball never tunnels, energy conservation so bounces feel real — because the whole payoff depends on trusting the scatter. A ball that clips through a peg or gains speed from a bounce breaks the illusion instantly; the ecstasy is only possible on a foundation the player never doubts.

Load-bearing structures

StructureWhy it works
One trivial input, cascading outputAim + drop is all the player does; physics + pegs generate the complexity. The effort/reward gap IS the fun.
Trustworthy swept-collision physicsClosed-form time-of-impact = no tunneling ever; energy honesty (a bounce never speeds the ball up) makes the scatter feel real, not glitchy. FUN.md truth. genre-physics-arcade.
Variable-ratio surpriseLucky multi-peg bounces and the free-ball bucket are unpredictable payoffs — the schedule that keeps you dropping “one more ball.” system-reward-schedules.
Disproportionate celebrationSlow-mo, zoom, orchestral sting, screen-filling explosion on the last orange peg — feedback far exceeds the input. pattern-juice-choreography.
Read the board, place the betSkill lives in choosing the shot — angling for clusters, banking off walls — turning luck into a decision. pattern-risk-reward.
Aim-search proves winnabilityPure state → clone-and-fire candidate aims → count clears: winnability AND a difficulty meter for free. FUN.md law 7.
Escalating per-ball scoringPoints ramp within a single drop (peg after peg), so even one ball has an arc. pattern-feedback-loops.

What to steal

What’s just theme (drop it)

Composes into

Twist seams

See also

This module rendersthe repo's markdowndirectly — edit it there, it changes here.