Building comparison
head to head
Quake IIvsRaiden V
Neither is meaningfully harder - they pose close to the same test. The widest gap is execution, and it is a single point.
Quake II
Execution · Pure Mechanics
A methodical shooter that rewards learning enemy layouts and conserving resources across connected military bases.
Raiden V
Execution · Pure Mechanics
A vertical bullet-hell shmup testing dodging precision against scripted patterns.
Quake II leans Execution (Pure Mechanics); Raiden V leans Execution (Pure Mechanics).
Quake IIRaiden V
Axis by axis
Execution8 vs 9
Raiden V leans a little harder on execution, though the gap is small.
Quake II
Fast strafe-aim against hard-hitting enemies demands clean inputs
Raiden V
Dodging bullet patterns while shooting is the entire skill
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Quake II
All enemies are scripted; no adaptive AI present
Raiden V
Enemies follow fixed scripted patterns, not adapting
Variance3 vs 2
Quake II leans a little harder on variance, though the gap is small.
Quake II
Item and enemy placement is fixed but unknown on first play
Raiden V
Patterns are memorizable, little true randomness
Optimization5 vs 5
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Quake II
Ammo and health economy tightly constrains routing through every level
Raiden V
Weapon selection and route learning is a meaningful layer
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.