gd-progression-design

Choose a curve type based on design intent: linear for predictable tutorials, exponential for mid-game engagement, polynomial for smooth acceleration, or S-curve for long-term retention. Then generate a level table with XP required, cumulative XP, unlocks, and estimated time per level.

Map the tree's branches, define prerequisites between nodes, and balance opportunity cost so every branch remains viable. Avoid obviously wrong paths by ensuring each branch offers comparable value for different playstyles.

A hard gate blocks access entirely until a condition like a level requirement is met. A soft gate allows access but makes content difficult, such as a recommended level, while a discovery gate hides content until triggered.

Use prestige systems when players exhaust endgame content and need a renewed motivation loop. The reset must feel like a meaningful choice with tangible prestige bonuses, not a punishment for progress.

Progression feels flat when level-ups lack visible rewards or pacing is too slow early on. Keep the first five levels under ten minutes total and ensure every level-up grants a visible reward, not just a number change.