Building comparison
head to head
80 DaysvsBeholder
Neither is meaningfully harder - they pose close to the same test. The widest gap is execution, and it is a single point.
80 Days
Optimization · Systems & Chaos
A narrative race around an alternate steampunk world balancing routes, money, and time.
Beholder
Optimization · Pure Optimization
Dystopian management adventure about a landlord spying on tenants for a totalitarian state.
80 Days leans Optimization (Systems & Chaos); Beholder leans Optimization (Pure Optimization).
80 DaysBeholder
Axis by axis
Execution0 vs 1
Beholder leans a little harder on execution, though the gap is small.
80 Days
Menu choices only, no physical skill
Beholder
Simple point-and-click landlord actions
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
80 Days
NPCs follow scripted branches, never adapt
Beholder
Tenants follow scripted schedules, not adaptive
Variance5 vs 4
80 Days leans a little harder on variance, though the gap is small.
80 Days
Unknown routes, events, and market prices on first runs
Beholder
Tenant events and directives surprise first runs
Optimization7 vs 7
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
80 Days
Routing, packing, and trading converge to optimal circumnavigations
Beholder
Money, time, and blackmail decision routing
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.