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

Optimization · Pure Optimization
The deepest optimization puzzle in the Infinity Engine lineage, rewarding encyclopedic knowledge of 2nd Edition AD&D systems.

Optimization · Pure Optimization
Engineering optimal Wanzer configurations and skill allocations to dominate scripted mech skirmishes.
Baldur's Gate II: Shadows of Amn 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.
Baldur's Gate II: Shadows of Amn
Pause-and-plan removes twitch entirely; micro-placement has marginal value
Front Mission 1st: Remake
Turn-based; no twitch; Wanzer part targeting is planning-based
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Baldur's Gate II: Shadows of Amn
Enemies run scripted behaviour patterns, never modelling your tactics
Front Mission 1st: Remake
Enemy AI is scripted per mission type
Same score on variance - which means the number cannot separate them. The difference is in what each one asks of you.
Baldur's Gate II: Shadows of Amn
Loot randomization and enemy ability use create hidden-information layers
Front Mission 1st: Remake
Hit rates and shield proc randomness create meaningful combat variance
Baldur's Gate II: Shadows of Amn leans a little harder on optimization, though the gap is small.
Baldur's Gate II: Shadows of Amn
Mage spell sequences, dual-class builds and Spellhold routing define mastery
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.