Building comparison
head to head
AladdinvsAssault Android Cactus
Neither is meaningfully harder - they pose close to the same test. The widest gap is execution, and it is a single point.
Aladdin
Execution · Pure Mechanics
A classic side-scrolling platformer following Aladdin through Agrabah and beyond.
Assault Android Cactus
Execution · Pure Mechanics
A high-intensity twin-stick shooter testing sustained aim and combo-chain routing.
Aladdin leans Execution (Pure Mechanics); Assault Android Cactus leans Execution (Pure Mechanics).
AladdinAssault Android Cactus
Axis by axis
Execution7 vs 8
Assault Android Cactus leans a little harder on execution, though the gap is small.
Aladdin
Precise platforming jumps and sword-timing are demanding.
Assault Android Cactus
Screen-filling enemy waves demand constant twin-stick precision
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Aladdin
No adaptive opponent, fixed enemy patterns.
Assault Android Cactus
Robot waves spawn on fixed scripts
Variance2 vs 2
Same score on variance - which means the number cannot separate them. The difference is in what each one asks of you.
Aladdin
Some randomness in enemy placement and drops.
Assault Android Cactus
Power-up drops add minor run-to-run noise
Optimization4 vs 5
Assault Android Cactus leans a little harder on optimization, though the gap is small.
Aladdin
Level routes are learnable but execution dominates.
Assault Android Cactus
Combo chains and battery routing are learnable scoring systems
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.