Building comparison
head to head
Darkest DungeonvsGoing Medieval
Neither is meaningfully harder - they pose close to the same test. The widest gap is execution, and it is a single point.
Darkest Dungeon
Optimization · Systems & Chaos
Gothic turn-based roguelike where managing stress and bad dice is the real fight.
Going Medieval
Optimization · Systems & Chaos
Constructing and defending a medieval fortress colony through randomised events and deep production chains.
Darkest Dungeon leans Optimization (Systems & Chaos); Going Medieval leans Optimization (Systems & Chaos).
Darkest DungeonGoing Medieval
Axis by axis
Execution0 vs 1
Going Medieval leans a little harder on execution, though the gap is small.
Darkest Dungeon
turn-based, no dexterity
Going Medieval
Pause-enabled management has no twitch component
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Darkest Dungeon
no adaptive opponent
Going Medieval
Raider AI follows scripted attack patterns and frequencies
Variance7 vs 6
Darkest Dungeon leans a little harder on variance, though the gap is small.
Darkest Dungeon
crits, stress events, and dungeon rolls punish plans
Going Medieval
Settler traits, weather, and plague events carry meaningful randomness
Optimization8 vs 8
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Darkest Dungeon
party comps and risk management are deeply solvable
Going Medieval
Fortress design, food supply chains, and research order are richly 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.