Building comparison
head to head
Getting Over It with Bennett FoddyvsStar Wars Episode I: Racer
Neither is meaningfully harder - they pose close to the same test. The widest gap is variance, and it is a single point.
Getting Over It with Bennett Foddy
Execution · Pure Mechanics
Infamous climbing game where one slip of the hammer undoes hours of progress.
Star Wars Episode I: Racer
Execution · Pure Mechanics
The podracing game whose risk-reward boost system creates a brutal pure-speed skill ceiling.
Getting Over It with Bennett Foddy leans Execution (Pure Mechanics); Star Wars Episode I: Racer leans Execution (Pure Mechanics).
Getting Over It with Bennett FoddyStar Wars Episode I: Racer
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.
Getting Over It with Bennett Foddy
Every inch climbed is precise hammer micro-control
Star Wars Episode I: Racer
Boost management at 600mph through canyons is pure hands.
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Getting Over It with Bennett Foddy
The mountain never adapts
Star Wars Episode I: Racer
AI racers follow fixed behaviour.
Variance0 vs 1
Star Wars Episode I: Racer leans a little harder on variance, though the gap is small.
Getting Over It with Bennett Foddy
Fully deterministic physics and terrain
Star Wars Episode I: Racer
Fixed tracks; nothing meaningful hidden.
Optimization3 vs 4
Star Wars Episode I: Racer leans a little harder on optimization, though the gap is small.
Getting Over It with Bennett Foddy
Route knowledge helps but cannot replace hands
Star Wars Episode I: Racer
Pod part upgrades and track memorization converge quickly.
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.