Building comparison
head to head
EarthBoundvsPokémon: Let's Go, Eevee!
Neither is meaningfully harder - they pose close to the same test. The widest gap is reads, and it is a single point.
EarthBound
Optimization · Pure Optimization
A subversive JRPG where understanding rolling HP mechanics and PSI optimization defeats its quirky scripted encounters.
Pokémon: Let's Go, Eevee!
Optimization · Systems & Chaos
A monster-collecting RPG where building an optimal team overshadows any twitch skill.
EarthBound leans Optimization (Pure Optimization); Pokémon: Let's Go, Eevee! leans Optimization (Systems & Chaos).
EarthBoundPokémon: Let's Go, Eevee!
Axis by axis
Execution2 vs 2
Same score on execution - which means the number cannot separate them. The difference is in what each one asks of you.
EarthBound
Rolling HP meter has very mild timing implication
Pokémon: Let's Go, Eevee!
minimal, catch motion controls light
Reads0 vs 1
Pokémon: Let's Go, Eevee! leans a little harder on reads, though the gap is small.
EarthBound
All enemies scripted with fixed attack patterns
Pokémon: Let's Go, Eevee!
trainer battles are scripted, minor human PvP
Variance4 vs 5
Pokémon: Let's Go, Eevee! leans a little harder on variance, though the gap is small.
EarthBound
PSI randomness, enemy attack variety, and encounter triggers add unpredictability
Pokémon: Let's Go, Eevee!
catch rates and stats have randomness
Optimization7 vs 7
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
EarthBound
Status effects, rolling HP strategy, and Franklin Badge usage are solvable
Pokémon: Let's Go, Eevee!
team building and type matchups solvable
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.