Building comparison
head to head
80 DaysvsCitizen Sleeper
Neither is meaningfully harder - they pose close to the same test. The widest gap is reads, and it is a single point.
80 Days
Optimization · Systems & Chaos
A narrative race around an alternate steampunk world balancing routes, money, and time.
Citizen Sleeper
Optimization · Systems & Chaos
A tabletop-flavored RPG about an android surviving on a derelict station.
80 Days leans Optimization (Systems & Chaos); Citizen Sleeper leans Optimization (Systems & Chaos).
80 DaysCitizen Sleeper
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.
80 Days
Menu choices only, no physical skill
Citizen Sleeper
Dice placement, no manual skill.
Reads0 vs 1
Citizen Sleeper leans a little harder on reads, though the gap is small.
80 Days
NPCs follow scripted branches, never adapt
Citizen Sleeper
NPCs follow branching scripts.
Variance5 vs 6
Citizen Sleeper leans a little harder on variance, though the gap is small.
80 Days
Unknown routes, events, and market prices on first runs
Citizen Sleeper
Daily dice rolls drive outcomes.
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
Citizen Sleeper
Action allocation and clock management dominate.
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.