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

Optimization · Pure Optimization
Optimizing pair-up chains and offspring builds to steamroll deterministically scripted maps.

Optimization · Pure Optimization
A d20 Star Wars RPG where Force power selection and alignment routing define clear optimal paths.
Fire Emblem Fates leans Optimization (Pure Optimization); Knights of the Old Republic 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.
Fire Emblem Fates
Turn-based menu play; no hand-speed demands
Knights of the Old Republic
Pseudo-turn-based d20 combat removes all twitch; timing aids exist but minor
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Fire Emblem Fates
AI follows scripted attack priorities, not player modeling
Knights of the Old Republic
All enemies follow scripted AI behaviour trees without player modelling
Fire Emblem Fates leans a little harder on variance, though the gap is small.
Fire Emblem Fates
Dual-strike/guard procs and hit rates inject meaningful RNG
Knights of the Old Republic
Loot rolls and pazaak draws provide hidden information layers
Knights of the Old Republic leans a little harder on optimization, though the gap is small.
Fire Emblem Fates
Offspring seals, asset/flaw selection, and supports are deeply planned
Knights of the Old Republic
Force power selection, feat prerequisites and light/dark routing are systematically 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.