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 · Mind & Math
Castle economics RTS where supply chain optimization and defensive geometry are tested against escalating siege pressure.

Optimization · Mind & Math
Tolkien RTS where build orders and army counters decide the war for Middle-earth.
Stronghold: Crusader leans Optimization (Mind & Math); The Lord of the Rings: The Battle for Middle-earth leans Optimization (Mind & Math).
Same score on execution - which means the number cannot separate them. The difference is in what each one asks of you.
Stronghold: Crusader
Troop rally timing and siege placement require practiced attention
The Lord of the Rings: The Battle for Middle-earth
Micro and multitasking under real-time pressure
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Stronghold: Crusader
Opponent lord AI has semi-scripted but varied attack patterns
The Lord of the Rings: The Battle for Middle-earth
Multiplayer rewards predicting opponent army choices
Stronghold: Crusader leans a little harder on variance, though the gap is small.
Stronghold: Crusader
Goods market prices and siege equipment availability fluctuate
The Lord of the Rings: The Battle for Middle-earth
Scouting hides enemy composition until revealed
Stronghold: Crusader leans a little harder on optimization, though the gap is small.
Stronghold: Crusader
Castle layout and goods production chains are deeply optimizable
The Lord of the Rings: The Battle for Middle-earth
Build orders and counter units are largely 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.
full breakdown
Stronghold: Crusader →
full breakdown
The Lord of the Rings: The Battle for Middle-earth →