Kingdom Come: Deliverance — The RPG That Trusts Its Own Friction

Henry of Skalitz cannot read. He cannot fight a trained soldier and expect to win. He gets drunk on two tankards and falls over in the street, and the game lets him wake up somewhere he doesn’t recognise with his coin purse lighter. None of this is a difficulty slider set too high. It is the entire pitch of Warhorse Studios’ 2018 debut, and it is why Kingdom Come: Deliverance remains the most interesting failure-state design an open-world RPG has attempted this decade.

The setup is 1403 Bohemia, a real kingdom mid-collapse: King Wenceslas IV imprisoned by his half-brother Sigismund of Hungary, whose mercenary army sacks border villages to fund the coup. Henry survives the sack of Skalitz, loses his parents to it, and spends the game as a blacksmith’s son thrown into a war he has no training for. That last clause is doing all the work. Most RPGs hand you a chosen one whose destiny excuses the power fantasy. Warhorse handed you a smith with good arms and no idea how a longsword actually moves, funded the whole project on Kickstarter and a promise of historical rigour, and then built every system around the gap between what Henry can physically do and what the plot needs of him.

The friction is the argument

Take the save system first, because it’s the one that generated the most noise on release. There is no free quicksave. You save by drinking a Saviour Schnapps, a craftable and purchasable item you carry in limited supply, or by sleeping in a bed you own. Complaints treated this as an oversight. It isn’t — it’s the same logic Warhorse applies to combat, lockpicking and reading, which is that convenience has to be earned or bought, never assumed. A game that let you save mid-lockpick would also be a game where lockpicking carries no tension. Remove the safety net and a fifteen-second minigame becomes a real decision about whether this chest is worth the risk, because a bad reload costs you real, measurable progress rather than a shrug and a retry.

Reading is the cleanest version of the idea. Henry starts illiterate, which locks him out of quest text, letters and eventually a whole diplomatic subplot, until you pay a scribe or a priest to teach him. It’s a stat gate dressed as a life circumstance, and it does something most stat gates don’t: it makes the player feel the specific, historically accurate poverty of a blacksmith’s son in a world where literacy was a genuine class marker rather than a given. Alchemy runs the same logic in the opposite direction — recipes are read off in-game books as a sequence of steps (chop, grind, add, boil, wait), and brewing a real potion means actually following that sequence at the cauldron rather than selecting an ingredient list from a menu. Get the order wrong and you’ve wasted the herbs. The game would rather you fail honestly than succeed by convention.

The sword fighting system

The combat is the part that took the longest to actually work, and it’s worth separating the idea from the initial execution. Warhorse built a directional system: five angles of attack and defence, matched with a stamina bar and a perk tree of combos, feints and master strikes. Fighting a trained soldier at low level is meant to be closer to a fencing lesson you’re losing than a power fantasy — you parry, you get read, you eat a counter-riposte, and the game wants you to notice exactly why you lost, down to the specific angle you left open.

The problem at launch was legibility: the directional cues were hard to read mid-fight, and the system rewarded knowledge the game hadn’t taught you yet, which read as unfairness rather than difficulty. Patches through 2018 fixed the clarity without softening the stakes, and what’s left is still one of the few first-person medieval combat systems that models a sword fight as a conversation rather than a meter race. Master strikes — a perfectly timed parry that opens a free hit — are the system’s thesis in miniature: reward a player who reads their opponent over one who simply mashes a button faster than the enemy can react. Captain Bernard’s early combat lessons exist for a mechanical reason as much as a narrative one: the game genuinely cannot be played competently without them, and it tells you so by making you lose to him repeatedly until the angles click.

Equipment decays with use in a way most RPGs fake. Armour gets dirty and loses effective protection until cleaned; weapons dull and need a whetstone; horses need feeding, brushing and a saddle that fits, or their stamina and speed suffer. None of it is punishing in isolation. Stacked together, it’s a constant low hum of upkeep that makes Henry’s growing competence feel earned rather than handed down by a level-up screen.

A world that keeps its own time

The quest design is where the friction philosophy pays its clearest dividend. Most open-world RPGs offer a stealth path, a combat path and a dialogue path as parallel tracks that converge on the same outcome. Kingdom Come is more interested in letting you improvise a solution nobody scripted a name for. Need to get into a bandit camp? You can fight your way in, sneak in after dark, disguise yourself in stolen bandit clothes and walk through the front gate, or simply talk your way past a guard who’s bored and underpaid. The bandit-clothes route is the one that best demonstrates the studio’s confidence: it works because NPCs check what you’re wearing before they check your face, which is a small piece of logic that quietly underwrites half the game’s stealth design.

NPCs keep schedules that persist whether or not you’re watching: the miller grinds grain in the morning, drinks in the tavern by evening, sleeps at night, and if you rob his house at 3am he’ll actually be in the bed you’re trying to loot next to. It’s not a revolutionary idea — Ultima and Gothic both did versions of it decades earlier — but Kingdom Come commits to it at a scale that makes Rattay and Talmberk feel inhabited rather than staged, and it means the “best” way to rob a house genuinely depends on knowing when its owner isn’t in it. The tavern dice game, Farkle, is a small, almost throwaway system by comparison, and it’s there for the same reason the alchemy sequencing is: because a world this committed to texture needs somewhere for Henry to just be a person killing an evening, not a quest-flag delivery mechanism.

Where it genuinely fights itself

Not every friction point earns its keep. The main quest’s early stealth sequence in Talmberk demands trial-and-error timing against guard patrols that the game doesn’t clearly telegraph, and the hunger/sleep/hygiene systems, while thematically justified, produce busywork stretches where you’re managing three meters instead of playing the RPG underneath them. Bugs at launch were real and well documented — physics glitches, quest triggers that silently failed, an infamous case of Henry’s horse Pebbles disappearing mid-quest — and while patches addressed the worst of it, some jank never fully left. The lockpicking minigame, borrowed wholesale from The Elder Scrolls, is the one system that feels imported rather than designed, a controller-unfriendly tension spring in a game otherwise built around considered, purposeful friction. It’s the single system in the whole design that feels like a placeholder nobody circled back to.

The real ancestor

The obvious comparison people reach for is The Witcher 3, and there’s a real conversation there — both are Central European, both put a grounded protagonist inside a collapsing kingdom, and I’ve made the case for what Geralt’s game does differently in my read on the side quest as the main event. But The Witcher 3 is fundamentally a fantasy power fantasy with a melancholy paint job — Geralt is already the best swordsman most people he meets have seen. Kingdom Come’s real ancestor is a system nobody under thirty has heard of: MicroProse’s Darklands (1992), a PC RPG set in a magic-realist Holy Roman Empire that modelled disease, saints’ relics and alchemical ingredient combination with the same fussy, simulationist seriousness Warhorse applies to sword angles and literacy. Both games share a conviction that historical texture is more interesting than a fantasy skin, and that a simulation should occasionally let you fail in a way that teaches you something rather than just costing you a health bar. Warhorse inherited that DNA without, as far as I know, ever citing it — which is usually how the best lineages work.

The verdict

Kingdom Come: Deliverance asks for patience its opening hours don’t fully reward. The tutorial village of Skalitz and the early Talmberk stretch are genuinely the worst hours in the game, front-loaded with systems the plot hasn’t yet given you a reason to care about, and a fair chunk of the “unplayable at launch” reputation traces to players bouncing off exactly that stretch before the combat clarity patches landed. Push past it and the game opens into Rattay, a proper market town with its own economy, court intrigue and a bathhouse subplot that’s funnier than it has any right to be, and the pacing problem mostly resolves itself. Its jank is real, too, not exaggerated by unhappy reviewers on release. But the underlying design — a low-fantasy RPG that treats illiteracy, drunkenness and a bad sword arm as legitimate player-facing systems rather than flavour text — hasn’t been matched since, including, arguably, by Warhorse’s own sequel. It’s still on PC, PlayStation and Xbox, patched to a stable state years on, and the Royal Edition bundling all four DLC campaigns is the version worth starting with. Skip the temptation to fast-forward through the tutorial village. The friction there is the whole pitch, and by the time you resent it, you’ve already learned to read it.

Spoilers below

The Skalitz massacre that opens the game is scripted to be unwinnable — Henry cannot save his parents, and the mission exists to establish that this world does not owe you a heroic save. That refusal to let an early fight go your way sets the tone for everything after: Sir Radzig’s retinue, the Cuman raiders, and eventually Sigismund’s occupying garrisons are threats you route around or out-think before you’re strong enough to meet head-on.

The main campaign ends without resolving the succession crisis — Wenceslas remains imprisoned, Sigismund’s grip on Bohemia is dented but not broken, and Henry’s personal arc closes on revenge against Runt, his father’s killer, rather than on a kingdom saved. It’s a deliberately unsatisfying historical note to end on, because the real 1403–1405 crisis didn’t resolve neatly either, and Warhorse chose accuracy over catharsis. The DLC campaigns — A Woman’s Lot, Band of Bastards, The Amorous Adventures of Bold Sir Hans — fill in the margins of that same unresolved war rather than closing it, and the game is better for having the discipline to leave the bow unstrung.