contextualPROGcanonical

Decide the mix of player skill and character power

GDC-L1-PROG-0002
Strong4/5

01

Statement

"Getting better" can come from two sources: the player improving (execution, knowledge, timing) or the character growing (stats, gear, unlocks). Decide the intended blend deliberately — it determines whether mastery is earned at the controller or accumulated on the character sheet.

02

Rationale

The two sources feel completely different. Player-skill progression rewards practice — muscle memory, pattern recognition, better decisions — and is satisfying because you got better [S-schell-artofgamedesign]. Character-power progression rewards investment — time, resources, choices — and is satisfying because your avatar can now do what it couldn't. Games sit somewhere on this axis, and the position shapes everything: difficulty tuning, how failure feels, whether a stuck player should grind or improve, and who the game is for. Leaving it unexamined produces incoherence — e.g. a game that asks for twitch skill but lets players out-level every challenge, satisfying neither the action player nor the RPG player.

03

Applies when

Any game with progression and any real-time challenge — action-RPGs especially, where the two sources are most in tension.

04

Does not apply / Exceptions

Pure-skill games (fighting games, most competitive shooters) deliberately sit at the player-skill pole with little character power; pure-build games and idle/incremental games sit near the character-power pole with little execution demand. Both extremes are coherent; the danger is an unintended muddle in the middle.

05

Implementation

Decide, per system, whether a challenge should be beaten by getting better or by getting stronger — and make the game's answer consistent so a stuck player knows what to do.

06

Disagreement

Action tradition (player skill is the point; character power should never trivialize execution) vs. RPG tradition (character growth is the fantasy; the sheet, not the thumbs, should decide outcomes). Both are valid design goals; the axis position is a defining choice, not a mistake.

07

Notes

Confidence 4.

Connected principles

S

Source trail