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.

Execution · Pure Mechanics
Twitch tank duels while protecting a base from scripted enemy waves.

Execution · Pure Mechanics
Landmark FPS built on physics puzzles and tight gunplay.
Battle City leans Execution (Pure Mechanics); Half-Life 2 leans Execution (Pure Mechanics).
Battle City leans a little harder on execution, though the gap is small.
Battle City
Tank aim and dodge timing under pressure decides every stage
Half-Life 2
Gravity gun and shooting demand precision.
Half-Life 2 leans a little harder on reads, though the gap is small.
Battle City
Enemy tanks follow simple scripted routines, nothing adaptive
Half-Life 2
Combine AI scripted, non-adaptive.
Battle City leans a little harder on variance, though the gap is small.
Battle City
Spawn order and power-ups add mild randomness per stage
Half-Life 2
Almost no randomness.
Battle City leans a little harder on optimization, though the gap is small.
Battle City
Base-defense positioning and brick management have known best answers
Half-Life 2
Linear progression with no builds.
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.