head to head
Neither is meaningfully harder - they pose close to the same test. The widest gap is variance, and it is a single point.

Optimization · Systems & Chaos
A solo poker roguelike about engineering scoring engines from a randomised shop.

Optimization · Pure Optimization
A systems-dense fortress survival game where mastery of deeply randomized simulation rules determines whether your dwarves live or die.
Balatro leans Optimization (Systems & Chaos); Dwarf Fortress leans Optimization (Pure Optimization).
Same score on execution - which means the number cannot separate them. The difference is in what each one asks of you.
Balatro
Drag-and-click cards; no mechanical demand at all.
Dwarf Fortress
Menu-driven with no physical performance ceiling whatsoever
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Balatro
No opponent; blinds are fixed scripted targets.
Dwarf Fortress
Goblins and megabeasts follow scripted aggression; no player modeling
Balatro leans a little harder on variance, though the gap is small.
Balatro
Shop offers and card draws gate every run.
Dwarf Fortress
World generation, artifact rolls, and siege timing carry deep randomness
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Balatro
Joker synergies and scoring math are the core puzzle.
Dwarf Fortress
Military, food chains, and fortress layout reward encyclopedic systems mastery
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.