Building comparison
head to head
Hollow KnightvsProject CARS
Neither is meaningfully harder - they pose close to the same test. The widest gap is reads, and it is a single point.
Hollow Knight
Execution · Practiced Mastery
A precision metroidvania about learning fixed boss patterns and tight platforming.
Project CARS
Execution · Practiced Mastery
Simulation driving precision underpinned by setup tuning and race strategy.
Hollow Knight leans Execution (Practiced Mastery); Project CARS leans Execution (Practiced Mastery).
Hollow KnightProject CARS
Axis by axis
Execution8 vs 8
Same score on execution - which means the number cannot separate them. The difference is in what each one asks of you.
Hollow Knight
Precise platforming and pogo timing dominate hard content.
Project CARS
Braking points and wheel control at the sim limit
Reads1 vs 2
Project CARS leans a little harder on reads, though the gap is small.
Hollow Knight
Bosses run scripted attack pools; not adaptive.
Project CARS
Online racecraft against humans adds light positional prediction
Variance1 vs 2
Project CARS leans a little harder on variance, though the gap is small.
Hollow Knight
Negligible; world layout is fixed.
Project CARS
Dynamic weather injects some session randomness
Optimization6 vs 6
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Hollow Knight
Charm builds and boss routes are fully learnable.
Project CARS
Setup tuning and pit strategy reward deep study
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.