Difficulty Curve Audit Checklist

🖨️ Print / Save as PDF

Difficulty problems almost always come down to two curves — expected player power and required encounter power — quietly disagreeing with each other. This checklist walks through mapping each curve, finding where they diverge, and checking for the specific mistakes that cause divergence most often. See all checklists and worksheets for related audits, including the full RPG progression checklist this one zooms in from.

Map Expected Player Power

• Define player power at each major content stage using realistic play patterns — average completion rate and average gear/level, not a best-case speedrun path.
• Pull actual telemetry where it exists rather than design-doc assumptions, since intended and actual pacing tend to drift apart once real content ships.
• Include optional-but-common sources of power (side content, crafting, a popular build) if a meaningful share of players actually use them before reaching each stage.
• Note the spread, not just the average — a wide gap between the 25th and 75th percentile player at a given stage means one fixed difficulty setting will fail a lot of people.
• Re-baseline this curve whenever early-game pacing changes, since a faster or slower start shifts expected power at every stage downstream.

Map Required Power Per Encounter

• For each boss or gated encounter, estimate the power actually required to clear it within a reasonable number of attempts, not the power required for a flawless clear.
• Separate raw stat-check difficulty (damage, health, resistances) from mechanical/skill difficulty, since the two need different fixes if a gap turns up.
• Check for encounters that assume a specific build, item, or ability the player may not have by that point, effectively raising required power above the intended baseline.
• Use the difficulty scaling calculator to model this curve numerically instead of relying on gut feel encounter by encounter.
• Confirm required power scales smoothly between major encounters rather than jumping only at boss fights, so minor content doesn't feel like a trivial gap between real tests.

Find the Gaps

• Plot expected player power and required power on the same axis and look for stages where the lines diverge rather than tracking each other.
• Treat a widening gap (player power pulling ahead) as a "too easy" signal — content stops feeling challenging even though nothing was explicitly nerfed.
• Treat a narrowing or crossing gap (required power pulling ahead) as a difficulty wall — this is usually where drop-off or frustration complaints cluster.
• Flag any stage where the gap changes size abruptly rather than gradually, since abrupt shifts usually mean one system was tuned in isolation from the rest.
• Cross-check gap locations against actual player drop-off or retry data if available — a mapped gap that doesn't show up in behavior may be smaller than it looks on paper.

Common Difficulty Mistakes to Check

• Check whether difficulty was tuned against internal testers who've played the encounter dozens of times rather than against a first-time player's realistic power and pattern knowledge.
• Look for one gate encounter that spikes far above the surrounding curve — a single wall like this does disproportionate damage to completion rates even if everything around it is well tuned.
• Verify difficulty settings (easy/normal/hard, if present) actually track the same required-power curve at different offsets, rather than only the default setting having been tuned carefully.
• Confirm difficulty has been re-validated after any content or economy change elsewhere in the game — a new gear tier, a currency change, or a buffed build can quietly move the expected-power curve without anyone retesting encounters against it. This is one of the most common hidden causes; see Preventing Power Creep for how it happens.
• Check that difficulty scaling tied to player level or gear (if the game auto-scales) is banded rather than fully continuous, so power gains between bands still feel felt instead of being immediately absorbed.

Illustrative example Say a mid-game boss was tuned by a designer who had cleared it dozens of times during development and knew every attack pattern cold. A first-time player with the same gear, but none of that pattern knowledge, needs meaningfully more effective power to clear it in a reasonable number of attempts — so the encounter reads as a difficulty wall for most players even though it tested fine internally. Mapping required power against a realistic (not expert) skill assumption is what catches this before launch.