Building comparison
head to head
Pokémon Blue VersionvsWartales
Neither is meaningfully harder - they pose close to the same test. The widest gap is reads, and it is a single point.
Pokémon Blue Version
Optimization · Pure Optimization
A solvable type-matchup system wrapped in collection and light RNG.
Wartales
Optimization · Pure Optimization
An open-world mercenary management RPG with grid-based tactical battles.
Pokémon Blue Version leans Optimization (Pure Optimization); Wartales leans Optimization (Pure Optimization).
Pokémon Blue VersionWartales
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.
Pokémon Blue Version
Menu battles have no physical component
Wartales
Turn-based tactics; no dexterity involved
Reads1 vs 0
Pokémon Blue Version leans a little harder on reads, though the gap is small.
Pokémon Blue Version
Trainer AI is fixed; only link battles add fleeting prediction
Wartales
Bandit AI follows predictable scripts
Variance3 vs 4
Wartales leans a little harder on variance, though the gap is small.
Pokémon Blue Version
Encounter rolls, catch rates and crits add mapped randomness
Wartales
Loot, recruits, and region events add hidden state
Optimization8 vs 8
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Pokémon Blue Version
Type chart and team building make the campaign solvable
Wartales
Party economy, professions, and positioning are deeply 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.