Building comparison
head to head
Mario + Rabbids Kingdom BattlevsPokémon Ruby Version
Neither is meaningfully harder - they pose close to the same test. The widest gap is execution, and it is a single point.
Mario + Rabbids Kingdom Battle
Optimization · Pure Optimization
Turn-based tactics where movement combos turn battles into solvable puzzles.
Pokémon Ruby Version
Optimization · Pure Optimization
Team-building optimisation against fixed trainers with mapped RNG.
Mario + Rabbids Kingdom Battle leans Optimization (Pure Optimization); Pokémon Ruby Version leans Optimization (Pure Optimization).
Mario + Rabbids Kingdom BattlePokémon Ruby Version
Axis by axis
Execution1 vs 0
Mario + Rabbids Kingdom Battle leans a little harder on execution, though the gap is small.
Mario + Rabbids Kingdom Battle
Turn-based; no dexterity gate
Pokémon Ruby Version
Turn selection requires no dexterity
Reads0 vs 1
Pokémon Ruby Version leans a little harder on reads, though the gap is small.
Mario + Rabbids Kingdom Battle
Enemy AI follows predictable rules
Pokémon Ruby Version
Scripted trainers never adapt to your strategy
Variance3 vs 3
Same score on variance - which means the number cannot separate them. The difference is in what each one asks of you.
Mario + Rabbids Kingdom Battle
Hit chances are mostly deterministic percentages
Pokémon Ruby Version
Encounter, catch and crit rolls are quickly mapped
Optimization8 vs 8
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Mario + Rabbids Kingdom Battle
Movement chains and team-jump routing are puzzle-solvable
Pokémon Ruby Version
Abilities and natures deepen an already solvable type system
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.