Building comparison
head to head
CupheadvsHollow Knight
Neither is meaningfully harder - they pose close to the same test. The widest gap is execution, and it is a single point.
Cuphead
Execution · Pure Mechanics
A run-and-gun boss rush about dodging scripted patterns with tight inputs.
Hollow Knight
Execution · Practiced Mastery
A precision metroidvania about learning fixed boss patterns and tight platforming.
Cuphead leans Execution (Pure Mechanics); Hollow Knight leans Execution (Practiced Mastery).
CupheadHollow Knight
Axis by axis
Execution9 vs 8
Cuphead leans a little harder on execution, though the gap is small.
Cuphead
Tight dodging and parry timing decide every boss.
Hollow Knight
Precise platforming and pogo timing dominate hard content.
Reads0 vs 1
Hollow Knight leans a little harder on reads, though the gap is small.
Cuphead
Bosses cycle scripted phases; no adaptation to player.
Hollow Knight
Bosses run scripted attack pools; not adaptive.
Variance1 vs 1
Same score on variance - which means the number cannot separate them. The difference is in what each one asks of you.
Cuphead
Minor attack-order shuffling between phases.
Hollow Knight
Negligible; world layout is fixed.
Optimization6 vs 6
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Cuphead
Loadouts and boss phase order are fully learnable.
Hollow Knight
Charm builds and boss routes are fully learnable.
A matching score does not mean a matching test. Two games can both sit at 10 on execution and demand completely different things of you - which is why the reasoning above matters more than the number beside it.