Building comparison
head to head
Blade RunnervsI'm on Observation Duty
Neither is meaningfully harder - they pose close to the same test. The widest gap is variance, and it is a single point.
Blade Runner
Variance · Systems & Chaos
Detective work against randomised suspect identities that reshuffle every playthrough.
I'm on Observation Duty
Variance · Systems & Chaos
A surveillance horror game testing spotting randomized anomalies across camera feeds.
Blade Runner leans Variance (Systems & Chaos); I'm on Observation Duty leans Variance (Systems & Chaos).
Blade RunnerI'm on Observation Duty
Axis by axis
Execution1 vs 1
Same score on execution - which means the number cannot separate them. The difference is in what each one asks of you.
Blade Runner
Point-and-click investigation, no dexterity required
I'm on Observation Duty
Clicking cameras - no twitch demands
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Blade Runner
Suspects follow branching scripts, not adaptive minds
I'm on Observation Duty
Anomalies are randomized, not a mind to predict
Variance6 vs 7
I'm on Observation Duty leans a little harder on variance, though the gap is small.
Blade Runner
Replicant identities are randomised each playthrough
I'm on Observation Duty
Which anomalies appear and where is hidden and random
Optimization5 vs 5
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Blade Runner
Evidence chains and questioning routes reward systematic detective work
I'm on Observation Duty
Systematic camera-checking routine converges to a checklist
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.