head to head
Neither is meaningfully harder - they pose close to the same test. The widest gap is execution, and it is a single point.

Optimization · Pure Optimization
Deep tactical build crafting and elemental combo solving across set-piece turn-based encounters.

Optimization · Pure Optimization
Team-building optimisation against fixed trainers with mapped RNG.
Divinity: Original Sin II - Definitive Edition leans Optimization (Pure Optimization); Pokémon Ruby Version leans Optimization (Pure Optimization).
Divinity: Original Sin II - Definitive Edition leans a little harder on execution, though the gap is small.
Divinity: Original Sin II - Definitive Edition
Turn-based combat removes any physical ceiling
Pokémon Ruby Version
Turn selection requires no dexterity
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Divinity: Original Sin II - Definitive Edition
Optional PvP arena aside, AI follows mappable behaviour
Pokémon Ruby Version
Scripted trainers never adapt to your strategy
Same score on variance - which means the number cannot separate them. The difference is in what each one asks of you.
Divinity: Original Sin II - Definitive Edition
Initiative rolls, random loot and unknown encounters add spice
Pokémon Ruby Version
Encounter, catch and crit rolls are quickly mapped
Divinity: Original Sin II - Definitive Edition leans a little harder on optimization, though the gap is small.
Divinity: Original Sin II - Definitive Edition
Build synergies, surface combos and positioning are deeply 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.