Building comparison
head to head
BIT.TRIP RUNNERvsVVVVVV
Neither is meaningfully harder - they pose close to the same test. The widest gap is variance, and it is a single point.
BIT.TRIP RUNNER
Execution · Pure Mechanics
Rhythm auto-runner where one missed beat sends you back to the start.
VVVVVV
Execution · Pure Mechanics
A brutal minimalist platformer where flipping gravity replaces jumping.
BIT.TRIP RUNNER leans Execution (Pure Mechanics); VVVVVV leans Execution (Pure Mechanics).
BIT.TRIP RUNNERVVVVVV
Axis by axis
Execution9 vs 9
Same score on execution - which means the number cannot separate them. The difference is in what each one asks of you.
BIT.TRIP RUNNER
One mistake restarts; rhythm-perfect input chains
VVVVVV
Pixel-perfect gravity flips through spike gauntlets
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
BIT.TRIP RUNNER
Obstacles are entirely fixed
VVVVVV
No opponent
Variance1 vs 0
BIT.TRIP RUNNER leans a little harder on variance, though the gap is small.
BIT.TRIP RUNNER
Fully deterministic level patterns
VVVVVV
Every hazard is fixed and visible
Optimization3 vs 3
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
BIT.TRIP RUNNER
Memorizing layouts and gold-bar routes
VVVVVV
Routes are short and obvious; execution is everything
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.