Building comparison
head to head
Battle CityvsSky Destroyer
Neither is meaningfully harder - they pose close to the same test. The widest gap is variance, and it is a single point.
Battle City
Execution · Pure Mechanics
Twitch tank duels while protecting a base from scripted enemy waves.
Sky Destroyer
Execution · Pure Mechanics
A simple arcade rail shooter testing aim and reaction against scripted waves.
Battle City leans Execution (Pure Mechanics); Sky Destroyer leans Execution (Pure Mechanics).
Battle CitySky Destroyer
Axis by axis
Execution7 vs 7
Same score on execution - which means the number cannot separate them. The difference is in what each one asks of you.
Battle City
Tank aim and dodge timing under pressure decides every stage
Sky Destroyer
Aiming and dodging on rails is the entire test
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Battle City
Enemy tanks follow simple scripted routines, nothing adaptive
Sky Destroyer
Enemy planes fly scripted attack runs
Variance2 vs 1
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
Sky Destroyer
Stages repeat predictably once seen
Optimization4 vs 3
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
Sky Destroyer
Little to plan beyond learning spawn patterns
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.