Building comparison
head to head
DOOM (2016)vsTetr.io
Tetr.io asks more than DOOM (2016), and the gap is reads.
DOOM (2016)
Execution · Pure Mechanics
Push-forward arena FPS where movement and aim are the whole game.
Tetr.io
Execution · Pure Mechanics
A competitive online stacker testing raw speed and versus stacking strategy.
DOOM (2016) leans Execution (Pure Mechanics); Tetr.io leans Execution (Pure Mechanics).
DOOM (2016)Tetr.io
Axis by axis
Execution8 vs 9
Tetr.io leans a little harder on execution, though the gap is small.
DOOM (2016)
Aim, movement, glory-kill timing all peak.
Tetr.io
Lightning-fast piece placement decides every match
Reads1 vs 3
Tetr.io leans clearly harder on reads.
DOOM (2016)
Demons scripted attack patterns.
Tetr.io
Human opponents in versus can be anticipated somewhat
Variance1 vs 2
Tetr.io leans a little harder on variance, though the gap is small.
DOOM (2016)
Minimal encounter randomness.
Tetr.io
Bag randomizer is bounded and quickly mappable
Optimization5 vs 5
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
DOOM (2016)
Rune and weapon mod picks meaningful.
Tetr.io
Stacking and garbage-management strategy underneath the speed
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.