The Anatomy of a Corpse Run: From Dark Souls to KUTO
A good corpse run gives the player one more decision after death. KUTO makes that decision personal by letting your own loadout stand between you and the loot.
What procedural generation is, the types and algorithms games use to build levels and worlds, and how it differs from plain random generation.
Procedural generation is a technique where a game creates its content — levels, terrain, loot, enemies, whole planets — using algorithms and rules at runtime, instead of a designer placing every piece by hand. Feed the system a starting number (a seed) and it assembles a fresh, playable result that stays inside the boundaries the designers set.
It's why a roguelike can hand you a different dungeon on your hundredth run, and why Minecraft can generate a world with more surface area than the Earth. Below is what the term actually means, how the algorithms work in plain language, and where the whole approach breaks down.
The word most people reach for is "random," and that's the misconception worth clearing up first. Procedural generation is closer to curated randomness. Designers build the raw materials — room templates, tile sets, item pools, enemy types, terrain rules — and write instructions for how those pieces fit together. An algorithm then combines them, usually starting from a seed, into something new that still obeys the rules.
So when a game is described as procedurally generated, it doesn't mean the developers threw dice and shipped whatever came up. It means they authored a system that assembles content on the fly, rather than authoring each finished level directly. The seed is the key detail: the same seed always produces the same output, which is why players can trade seed codes to replay a friend's exact world, and why a developer can reproduce a bug by re-running the layout that caused it.
The craft lives in the constraints. A weak system produces mush; a strong one produces variety that still feels intentional.
These get used interchangeably, but they're not the same thing, and the difference is the whole reason procedural generation works.
Random generation picks values with no rules attached. Roll for a number, place a wall, move on. Left to itself, that approach happily seals the exit behind an unbreakable wall, drops you into a room with no doors, or stacks three elite enemies on the starting tile.
Procedural generation wraps that randomness in rules and constraints applied to curated pieces. It might still roll for a room, but it checks that a path exists from entrance to exit, that the loot on offer is winnable-with, and that the difficulty lands in an acceptable band. Randomness is the engine; the constraints are the steering.
Put simply: randomness is a coin flip, procedural generation is a coin flip with a designer standing over it saying "not that one." Every good procedural system is really a set of guardrails around a random number.
"Procedural generation" is an umbrella. Games apply it to very different parts of their content, and most big titles use several kinds at once.
You don't need to write these to understand what a game is doing. Here are the workhorses, in plain terms.
Most real games chain several of these: noise for the terrain, cellular automata for the caves inside it, an L-system for the forests on top.
The cost is authored intent. A hand-built level can have a deliberate rhythm — a quiet stretch before an ambush, a view framed just so, an enemy placed to catch you exactly when you're low on health. A generated one trades some of that craft for variety, and when the constraints are weak the result feels samey, "soulless," or incoherent, like a puzzle assembled from mismatched pieces.
The honest failure mode is the "wide but shallow" world: technically endless, emotionally flat. No Man's Sky at launch is the cautionary tale — quintillions of planets that started to blur together after a few dozen.
That's why the strongest procedural games are usually hybrids. Spelunky and Dead Cells generate the overall layout but assemble it from rooms a human designed and tuned, so every run is fresh yet every room is fair. The generator handles arrangement; a person still handles the craft inside each piece. Even Dwarf Fortress and Caves of Qud, about as procedural as games get, lean on hand-authored systems, art, and rules underneath — the generator multiplies the designers' work rather than replacing it. It also changes how death and restarting feel: a generated world means starting over is a new problem, not a repeat of the last one.
In KUTO: The Lock of Time — our game — we sit on that hybrid end of the spectrum. The eras you fight through — Ancient Egypt, the Viking age, a neon cyber-city — are handcrafted layouts rather than fully generated ones, then varied so encounters with the Scythe of Kronos and your chosen time powers don't play out identically every attempt. It's authored space with room for variety, not a procedural roguelike. Wishlist KUTO on Steam.
A good corpse run gives the player one more decision after death. KUTO makes that decision personal by letting your own loadout stand between you and the loot.
Bullet time is easy to add and easy to ruin. The only interesting version is the one that still has to fight for its place in the loop.
Breaking things in games is usually consequence-free. In some games, it's a decision you'll feel for the rest of the run.
Death in roguelikes isn't a bug in the design. It's the design. Here's how the best games make dying feel deliberate.
Why one game's sword swing feels amazing and another's feels like waving a stick. The invisible craft of game feel, and what makes combat satisfying.