Building comparison
head to head
BeholdervsPokémon Quest
Neither is meaningfully harder - they pose close to the same test. The widest gap is variance, and it is a single point.
Beholder
Optimization · Pure Optimization
Dystopian management adventure about a landlord spying on tenants for a totalitarian state.
Pokémon Quest
Optimization · Systems & Chaos
Grinding random stone drops into stat loadouts that auto-battles then resolve.
Beholder leans Optimization (Pure Optimization); Pokémon Quest leans Optimization (Systems & Chaos).
BeholderPokémon Quest
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.
Beholder
Simple point-and-click landlord actions
Pokémon Quest
Auto-battling needs only occasional taps
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Beholder
Tenants follow scripted schedules, not adaptive
Pokémon Quest
Wild cube Pokémon follow simple scripts
Variance4 vs 5
Pokémon Quest leans a little harder on variance, though the gap is small.
Beholder
Tenant events and directives surprise first runs
Pokémon Quest
Cooking ingredients and stone drops are random
Optimization7 vs 6
Beholder leans a little harder on optimization, though the gap is small.
Beholder
Money, time, and blackmail decision routing
Pokémon Quest
Power stone loadouts and team stats decide expeditions
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.