head to head
Neither is meaningfully harder - they pose close to the same test. The widest gap is variance, and it is a single point.

Optimization · Pure Optimization
Turn-based tactics where movement combos turn battles into solvable puzzles.

Optimization · Pure Optimization
Engineering a beaver colony's water and food systems to survive scheduled drought cycles at growing scale.
Mario + Rabbids Kingdom Battle leans Optimization (Pure Optimization); Timberborn leans Optimization (Pure Optimization).
Same score on execution - which means the number cannot separate them. The difference is in what each one asks of you.
Mario + Rabbids Kingdom Battle
Turn-based; no dexterity gate
Timberborn
Construction and management require no physical precision
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Mario + Rabbids Kingdom Battle
Enemy AI follows predictable rules
Timberborn
No adversary exists; droughts are scheduled, not adaptive
Timberborn leans a little harder on variance, though the gap is small.
Mario + Rabbids Kingdom Battle
Hit chances are mostly deterministic percentages
Timberborn
Map seed and drought timing carry moderate session-level randomness
Timberborn leans a little harder on optimization, though the gap is small.
Mario + Rabbids Kingdom Battle
Movement chains and team-jump routing are puzzle-solvable
Timberborn
Water management, district planning, and beaver worker routing are the engineered core
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.