Building comparison
head to head
Orcs Must Die!vsTransistor
Neither is meaningfully harder - they pose close to the same test. The widest gap is reads, and it is a single point.
Orcs Must Die!
Optimization · Pure Optimization
A third-person tower defense about funneling orc hordes into gleefully lethal trap corridors.
Transistor
Optimization · Pure Optimization
A hybrid real-time and tactical action RPG in a digital city.
Orcs Must Die! leans Optimization (Pure Optimization); Transistor leans Optimization (Pure Optimization).
Orcs Must Die!Transistor
Axis by axis
Execution4 vs 4
Same score on execution - which means the number cannot separate them. The difference is in what each one asks of you.
Orcs Must Die!
Active shooting supplements the traps
Transistor
Real-time and planned hybrid combat.
Reads0 vs 1
Transistor leans a little harder on reads, though the gap is small.
Orcs Must Die!
Orc waves follow fixed paths
Transistor
Process enemies follow 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.
Orcs Must Die!
Minor wave composition randomness
Transistor
Limited randomness.
Optimization8 vs 7
Orcs Must Die! leans a little harder on optimization, though the gap is small.
Orcs Must Die!
Trap placement and kill-corridor economics are the game
Transistor
Function loadouts have deep optimization.
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.