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

Optimization · Pure Optimization
The genre-defining loot ARPG whose builds, runes, and trade economy players still optimize decades later.

Optimization · Pure Optimization
Engineering optimal Wanzer configurations and skill allocations to dominate scripted mech skirmishes.
Diablo II leans Optimization (Pure Optimization); Front Mission 1st: Remake 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.
Diablo II
Positioning and potion reflexes, little else physical
Front Mission 1st: Remake
Turn-based; no twitch; Wanzer part targeting is planning-based
Front Mission 1st: Remake leans a little harder on reads, though the gap is small.
Diablo II
Monster AI is fully mappable
Front Mission 1st: Remake
Enemy AI is scripted per mission type
Diablo II leans a little harder on variance, though the gap is small.
Diablo II
Loot RNG and random maps drive the grind
Front Mission 1st: Remake
Hit rates and shield proc randomness create meaningful combat variance
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Diablo II
Builds, breakpoints, rune economy, magic-find routing are the game
Front Mission 1st: Remake
Wanzer part builds, weapon loadouts, and pilot skill allocation are the game
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.