Building comparison
head to head
BeholdervsThe Count Lucanor
Neither is meaningfully harder - they pose close to the same test. The widest gap is execution, and it is a single point.
Beholder
Optimization · Pure Optimization
Dystopian management adventure about a landlord spying on tenants for a totalitarian state.
The Count Lucanor
Optimization · Systems & Chaos
A pixel-art horror fairy tale where a boy explores a cursed castle to win a kobold's inheritance.
Beholder leans Optimization (Pure Optimization); The Count Lucanor leans Optimization (Systems & Chaos).
BeholderThe Count Lucanor
Axis by axis
Execution1 vs 2
The Count Lucanor leans a little harder on execution, though the gap is small.
Beholder
Simple point-and-click landlord actions
The Count Lucanor
Light stealth evasion needs only basic movement
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
The Count Lucanor
Castle monsters patrol fixed routes without adaptation
Variance4 vs 4
Same score on variance - which means the number cannot separate them. The difference is in what each one asks of you.
Beholder
Tenant events and directives surprise first runs
The Count Lucanor
Unknown castle secrets and endings on a blind run
Optimization7 vs 6
Beholder leans a little harder on optimization, though the gap is small.
Beholder
Money, time, and blackmail decision routing
The Count Lucanor
Candle placement, puzzles, and ending routes are solvable
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.