head to head
Neither is harder. They score identically on all four axes, so the difference between them is in kind, not degree.

Optimization · Pure Optimization
Building a team and exploiting type-matchup math against scripted trainers.

Optimization · Pure Optimization
A choice-driven RPG where allocating stats toward Tide alignment and crisis routing determines narrative outcomes.
Pokémon LeafGreen Version leans Optimization (Pure Optimization); Torment: Tides of Numenera 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.
Pokémon LeafGreen Version
Menu-driven turn battles demand no physical skill
Torment: Tides of Numenera
Combat is explicitly optional; minimal motor demand throughout
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Pokémon LeafGreen Version
Trainers are scripted; link battles are a side mode
Torment: Tides of Numenera
Crisis encounters use scripted AI patterns, no adaptive opponents
Same score on variance - which means the number cannot separate them. The difference is in what each one asks of you.
Pokémon LeafGreen Version
Wild encounters, catch rolls and crits add mappable RNG
Torment: Tides of Numenera
Hidden Tide value thresholds and item interactions create unknown-information branches
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Pokémon LeafGreen Version
Type matchups and team building are the solvable core
Torment: Tides of Numenera
Stat allocation, Tide routing and artefact loadout reward system knowledge
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.