Random events
Scripted or semi-scripted incidents fire during play — a distress call, a plague, a wandering merchant, a moral dilemma — injecting surprise and narrative texture into systemic games. FTL's beacon events, RimWorld's storyteller incidents, and Crusader Kings' event chains all use randomness to keep runs unpredictable and personal. Designers use random events to break monotony, to create emergent-feeling stories from authored content, to present interesting choices with uncertain outcomes, and to pace tension. Key decisions: how much is choice-driven versus pure luck, weighting and gating so events fit the current context (RimWorld's 'storyteller' shapes event flow toward drama), event-chain depth (one-off versus branching consequences), and the balance of positive, negative, and dilemma events. Pitfall: events that feel arbitrary or unfair — a random catastrophe the player couldn't prevent or prepare for — read as the game cheating; the best random events either offer a choice, reward preparation, or arrive with enough warning that the outcome feels like a consequence rather than a dice roll.
- Dev effort: Medium
- Timing: Real-time or turn-based
- Common in: roguelike, colony-sim, grand-strategy
Seen in
- FTL: Faster Than Light
- RimWorld
- Crusader Kings III