What the game is
A procedurally generated, open-ended simulation and roguelike built around three interlinked modes—Fortress, Adventure, and Legends—all operating within a single persistent world. It uses ASCII-based visuals (code page 437) and rejects win conditions in favour of emergent, often tragic, storytelling.
How it actually plays
You generate a world first—continents, oceans, civilisations, histories—then pick a site for your fortress. You start with seven dwarves, livestock, and supplies. You do not control dwarves directly. You designate tasks: dig here, stockpile there, forge steel, brew booze. Dwarves execute them autonomously, governed by individual personalities, likes, dislikes, and trainable labour skills. Threats arrive unannounced: goblin sieges, forgotten beasts, magma floods. In Adventure mode, you control one character turn-by-turn across the same world, roaming, questing, fighting with anatomically detailed combat logs. Legends mode lets you read the world’s full history—including every dwarf who lived, died, or achieved something in your sessions.
What works
The world generation produces coherent, layered geographies—elevation, rainfall, drainage, temperature, mineral distribution—before any play begins. Every dwarf has an individual personality, trainable skills, and autonomous behaviour that reacts meaningfully to environment and stress. Combat is anatomically specific: logs name organs pierced, fat bruised, limbs severed. Legends mode records everything—player actions, dwarf deaths, siege outcomes—as permanent entries in the world’s documented history. The three modes share one world state: a fortress collapse appears in Legends; an adventurer’s slaying of a dragon alters the same world’s lore.
What does not
It does not guide you. There is no tutorial, no objective, no feedback loop that confirms you are doing it right. The ASCII interface offers no visual orientation—no map legend, no consistent symbol set across contexts, no spatial memory aid. World generation parameters like savagery or history length are adjustable but not explained. Combat logs describe severed limbs and pierced organs but give no tactical feedback. You cannot pause Fortress mode. You cannot save mid-adventure encounter. You cannot undo a misdesignated mine shaft.
Who it is for, and who it is not
It is for players who treat systems as texts to be read, not puzzles to be solved. It is for those who find meaning in failure, who enjoy interpreting cause-and-effect across layers of simulation, and who accept that clarity is earned, not granted. It is not for players who need signposting, feedback, or closure. It is not for those who expect interface consistency, visual legibility, or recoverable mistakes.
Is it worth your time
Yes—if you want to spend evenings wrestling with deep simulation, not chasing goals. It asks for patience, tolerance of opacity, and appetite for systemic tragedy over narrative payoff. It does not ask for reflexes, speed, or completion. It asks you to observe, interpret, and persist—not to win.