Overview
Progression curves fail when the pacing is wrong. The player gains 5 levels in the first hour and 1 level in the next 10 hours. The early game feels rewarding (constant level-ups, new abilities, visible power increases) and the late game feels punishing (hours between levels, marginal power increases, no visible progress). The player associates the game with the feeling of the late game — slow, unrewarding, grindy — even though the early game was well-paced.
The Progression Curve Engineering prompt builds XP and power curves with three properties: (1) pacing validation — the time between progression milestones is calculated and compared against target pacing (e.g., "new ability every 45-60 minutes, level-up every 30-90 minutes depending on stage"), (2) power-per-level calibration — the power increase per level is designed to produce a noticeable but not overwhelming difference (the player at level 10 should feel stronger than the player at level 9, but not so much stronger that level 9 content is trivialized), and (3) stage-appropriate acceleration — the curve accelerates or decelerates at specific game stages to produce the intended experience (fast early progression for onboarding, moderate mid-game for exploration, slow late-game for mastery and commitment).
What you get: - XP curve formula with stage-specific parameters - Power-per-level scaling model with perceptibility thresholds - Pacing validation table (time between milestones at each stage) - Milestone distribution map (abilities, unlocks, content gates per level) - Progression feel audit (does each stage produce the intended feeling?) - Catch-up mechanism specification (how late-joining players reach the curve)
Built for: systems designers, progression designers, and live ops teams who need curves that produce the right pacing at every game stage — not just the first 5 hours.