Building comparison
head to head
CupheadvsSalamander
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.
Salamander
Execution · Practiced Mastery
Arcade shmup reflexes welded to frame-perfect stage memorisation.
Cuphead leans Execution (Pure Mechanics); Salamander leans Execution (Practiced Mastery).
CupheadSalamander
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.
Salamander
Bullet weaving and terrain dodging at arcade pace
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Cuphead
Bosses cycle scripted phases; no adaptation to player.
Salamander
Enemy waves are scripted to the frame
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.
Salamander
Identical attract-mode determinism every credit
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.
Salamander
Memorising stage layouts and power-up routes is survival
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.