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
Optimizing pair-up chains and offspring builds to steamroll deterministically scripted maps.

Optimization · Pure Optimization
A blade-driven JRPG won by chain-attack routing and combo optimization.
Fire Emblem Fates leans Optimization (Pure Optimization); Xenoblade Chronicles 2 leans Optimization (Pure Optimization).
Xenoblade Chronicles 2 leans a little harder on execution, though the gap is small.
Fire Emblem Fates
Turn-based menu play; no hand-speed demands
Xenoblade Chronicles 2
Auto-attack with art-timing inputs
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
Xenoblade Chronicles 2
Scripted enemies
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
Xenoblade Chronicles 2
Blade gacha and crit rolls
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Fire Emblem Fates
Offspring seals, asset/flaw selection, and supports are deeply planned
Xenoblade Chronicles 2
Blade combos and chain attack routing central
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.