Building comparison
head to head
428: Shibuya ScramblevsOrwell: Keeping an Eye on You
Neither is meaningfully harder - they pose close to the same test. The widest gap is variance, and it is a single point.
428: Shibuya Scramble
Optimization · Pure Optimization
A live-action visual novel weaving five strangers' stories together across one chaotic day in Shibuya.
Orwell: Keeping an Eye on You
Optimization · Systems & Chaos
Surveillance thriller where you decide which citizens' secrets to report to the state.
428: Shibuya Scramble leans Optimization (Pure Optimization); Orwell: Keeping an Eye on You leans Optimization (Systems & Chaos).
428: Shibuya ScrambleOrwell: Keeping an Eye on You
Axis by axis
Execution0 vs 0
Same score on execution - which means the number cannot separate them. The difference is in what each one asks of you.
428: Shibuya Scramble
Reading and choosing only
Orwell: Keeping an Eye on You
Reading and clicking documents only
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
428: Shibuya Scramble
No opponent, only branching script
Orwell: Keeping an Eye on You
Story characters are scripted, not adaptive
Variance3 vs 4
Orwell: Keeping an Eye on You leans a little harder on variance, though the gap is small.
428: Shibuya Scramble
Cross-character consequences hidden until triggered
Orwell: Keeping an Eye on You
Truth is hidden until you uncover contradicting datachunks
Optimization6 vs 5
428: Shibuya Scramble leans a little harder on optimization, though the gap is small.
428: Shibuya Scramble
Mapping timeline interactions to dodge bad endings
Orwell: Keeping an Eye on You
Choosing which evidence to upload steers fixed outcomes
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.