Building comparison
head to head
Papers, PleasevsSystem Shock
Neither is meaningfully harder - they pose close to the same test. The widest gap is execution, and it is a single point.
Papers, Please
Optimization · Pure Optimization
Dystopian border-checkpoint sim where stamping passports fast enough feeds your family.
System Shock
Optimization · Practiced Mastery
Methodically mapping a hostile station where knowledge and routing beat reflexes.
Papers, Please leans Optimization (Pure Optimization); System Shock leans Optimization (Practiced Mastery).
Papers, PleaseSystem Shock
Axis by axis
Execution4 vs 5
System Shock leans a little harder on execution, though the gap is small.
Papers, Please
Document-checking speed directly pays the rent
System Shock
Combat and cyberspace ask competent but dated reflexes
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Papers, Please
Entrants are generated, not adaptive opponents
System Shock
SHODAN's threats are scripted, not an adapting mind
Variance4 vs 3
Papers, Please leans a little harder on variance, though the gap is small.
Papers, Please
Random entrant documents and scripted-event surprises
System Shock
Citadel's layout and logs are hidden until uncovered
Optimization7 vs 7
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Papers, Please
Internalizing rulebooks and inspection workflow efficiency
System Shock
Inventory, routing and station knowledge solve the game
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.