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 colorful loot ARPG where theorycrafting builds beats anything your hands do.
Fire Emblem Fates leans Optimization (Pure Optimization); Torchlight II leans Optimization (Pure Optimization).
Torchlight II leans a little harder on execution, though the gap is small.
Fire Emblem Fates
Turn-based menu play; no hand-speed demands
Torchlight II
Faster combat asks for dodging and skill timing
Fire Emblem Fates leans a little harder on reads, though the gap is small.
Fire Emblem Fates
AI follows scripted attack priorities, not player modeling
Torchlight II
Enemies are scripted swarms, never adaptive
Same score on variance - which means the number cannot separate them. The difference is in what each one asks of you.
Fire Emblem Fates
Dual-strike/guard procs and hit rates inject meaningful RNG
Torchlight II
Loot rolls and random maps drive the chase
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
Torchlight II
Skill trees and gear synergies decide character power
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.