Building comparison
head to head
Disco ElysiumvsPokémon Blue Version
Neither is meaningfully harder - they pose close to the same test. The widest gap is variance, and it is a single point.
Disco Elysium
Optimization · Pure Optimization
A dialogue RPG resolved by stat builds against dice checks.
Pokémon Blue Version
Optimization · Pure Optimization
A solvable type-matchup system wrapped in collection and light RNG.
Disco Elysium leans Optimization (Pure Optimization); Pokémon Blue Version leans Optimization (Pure Optimization).
Disco ElysiumPokémon Blue Version
Axis by axis
Execution0 vs 0
Same score on execution - which means the number cannot separate them. The difference is in what each one asks of you.
Disco Elysium
No mechanical inputs of consequence
Pokémon Blue Version
Menu battles have no physical component
Reads1 vs 1
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Disco Elysium
Dialogue partners are scripted, not modeling you
Pokémon Blue Version
Trainer AI is fixed; only link battles add fleeting prediction
Variance4 vs 3
Disco Elysium leans a little harder on variance, though the gap is small.
Disco Elysium
Skill checks roll dice with hidden modifiers
Pokémon Blue Version
Encounter rolls, catch rates and crits add mapped randomness
Optimization7 vs 8
Pokémon Blue Version leans a little harder on optimization, though the gap is small.
Disco Elysium
Build skills and route choices to pass checks
Pokémon Blue Version
Type chart and team building make the campaign 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.