RPG Progression Checklist

This is a practical checklist for auditing an RPG's progression system — leveling pace, gear power, skill trees, and difficulty alignment — either before shipping or as a mid-project sanity check. For the full reasoning behind each item, see How to Balance RPG Progression. If an audit turns up something that needs a deeper look, GameMender offers a free consultation to talk through your specific system.

Use this as a working checklist, not a scoring rubric — the goal is to surface specific problem areas, not produce a pass/fail grade. It's most useful when you can check items against real playtest sessions or telemetry rather than intended design values, since the two tend to drift apart as content gets built. See all checklists and worksheets for related audits, including a dedicated worksheet for XP curve math and a standalone difficulty curve audit.

Leveling Pace

Confirm actual (not intended) time-to-level at several checkpoints, using playtest or telemetry data rather than design-doc assumptions.
Check that leveling pace matches content cadence — players shouldn't hit a new level with nothing new to use it on, or run out of levels before running out of content.
Verify the XP curve's shape (linear, exponential, or hybrid) matches the intended early-game vs. late-game feel; see the XP curve design guide for the underlying math.
Look for any stretch where XP-per-level rises or falls sharply relative to neighboring levels, which usually signals an untested seam between tuning passes.
Confirm XP earn rate (not just XP required) is consistent across different playstyles, so one viable approach isn't accidentally starved.
Re-check pacing after any content patch — new quests, zones, or events shift effective earn rate even if the level curve formula didn't change.

Gear & Power Curve

Plot gear power by tier and confirm each tier is a clear, legible upgrade over the last rather than a marginal or ambiguous one.
Check for any gear tier that's a straight sidegrade with no clear reason to equip it, which tends to sit unused.
Verify there's a visible acquisition path to the next gear tier at every stage — no dead zones where nothing meaningful drops or unlocks.
Confirm gear power doesn't outrun difficulty far enough that a full tier can be skipped without consequence.
Check whether stat inflation from gear compounds with level-based stat growth in a way nobody explicitly tuned for.
Audit whether cosmetically distinct gear at the same tier is actually power-equivalent, or whether one option is quietly dominant.

Skill Trees & Meaningful Choices

List the distinct build archetypes the tree is meant to support, and confirm each has a coherent, competitive path through it.
For each node, ask whether there's any archetype for which it's the best available pick in its slot — flag any node with none as a likely trap.
Check early nodes specifically for traps, since a bad pick in the first hour damages player trust more than one made later with more context.
Confirm mutually exclusive choices (one node blocking another) are close enough in power that the choice feels meaningful rather than obviously correct.
Verify respec cost or availability matches how experimental you want players to feel about their choices.

Difficulty Alignment

At each major checkpoint, compare actual player power (from real data) against the power the next stretch of content assumes.
Confirm the gap between player power and required power stays roughly constant across the game rather than widening or narrowing sharply.
If enemies scale with player level, confirm scaling is banded by zone or tier rather than fully automatic, so power gains still feel felt.
Check for a specific level range or gear tier where difficulty spikes or flattens unexpectedly — this is usually where progression complaints cluster.
Re-run this comparison after any balance patch to gear, XP, or enemy stats, since all three can shift the gap independently.

FAQ: RPG Progression Checklist

When should I run this checklist during development?

Ideally at two points: once when the progression systems are playable end-to-end (even with placeholder content), and again a few weeks before launch once real content and tuning data exist. Running it only at the end means any structural issues — like a skill tree with dead nodes — are expensive to fix because content has already been built around them.

What's the single most common progression failure this checklist catches?

A widening or narrowing gap between player power and required power at some stage of the game — usually because leveling, gear, and skill trees were tuned separately instead of against one shared difficulty curve. It shows up as a section of the game that suddenly feels trivial or suddenly feels like a wall.

Do I need analytics data to use this checklist, or can I do it by feel?

You can start by feel — playtesting with fresh eyes catches a lot. But several items (leveling pace vs. content cadence, actual vs. intended player power at each stage) are far more reliable with real telemetry, since intended and actual pacing tend to drift apart during development. Use feel to flag suspects, then confirm with data where you have it.

This checklist mentions skill tree "trap" nodes — how do I find them without a full statistical pass?

Ask, for each node, whether there is any build archetype for which it's the best available choice in its slot. If a node is weak compared to its neighbors in every archetype you can think of, it's a candidate trap even before you run the numbers. A full statistical pass is worth doing eventually, but this question alone catches most of them.