roguelike

1# Roguelike
2 
3A playbook for roguelikes — the turn engine, procedural dungeons, field-of-view, permadeath,
4and run economy. This is a **compositional** skill: it orchestrates procedural generation,
5tilemaps, save handling, and AI into a run-based game. It does not re-teach noise/RNG or
6tilemap APIs; it defines the loop and the systems that make a *run* compelling.
7 
8## When to use
9 
10- Use when building a **turn-based, grid-based** dungeon crawler where each death ends the
11  run and the world is regenerated — a roguelike or "roguelite" (with meta-progression).
12- Use when designing procedural dungeons, FOV/fog-of-war, permadeath stakes, or loot tables.
13 
14**When *not* to use:** real-time action with roguelike *dressing* → build the action genre
15(`platformer`/`fps-shooter`) and layer `procedural-gen`. Deep stats/quests/dialogue without
16permadeath → `rpg`. Open-world needs/crafting → `survival-crafting`.
17 
18## What makes it a roguelike (design anchor)
19 
20The community reference is the **Berlin Interpretation** (RogueBasin, IRDC 2008): a set of
21"roguelikeness" factors, not a checklist. The high-value ones are the design targets:
22**random environment generation, permadeath, turn-based, grid-based, non-modal** (all actions
23in one mode), **complexity** (many item/monster interactions), **resource management**,
24**hack-and-slash**, and **exploration & discovery**. Lean into these to feel roguelike; pick
25which to keep deliberately. "Roguelite" usually relaxes permadeath with meta-progression.
26…