GAME MECHANICS HOARD

SEED-BASED RANDOMNESS

Random generation driven by a shareable seed value — the same seed producing the identical world, dungeon, or run every time, making randomness reproducible on demand.

Minecraft seeds are folk culture (communities catalog and trade world seeds like addresses), roguelikes run daily seeds so every player faces the same run (Spelunky's daily challenge made death singular and communal — one attempt, same caves, global leaderboard), speedrunning splits into seeded and unseeded categories as distinct disciplines, and Slay the Spire's custom seeds power puzzle-sharing and streak verification. Designers expose seeds because reproducibility transforms randomness from weather into text: a seed is a citation — players can share the incredible world, rerun the brutal dungeon, verify the record wasn't luck-fished, and compete on identical terrain where outcome differences are pure skill. The daily-seed format is the masterstroke: it converts a single-player roguelike into a synchronous community event (everyone dies in the same cave today, and the conversation writes itself), while costing the developer nothing but a date-hashed integer. Seeds also serve development itself — reproducible generation is debuggable generation — and enable the racing formats (seeded head-to-head) that give randomness-heavy games a spectator-fair competitive layer. Key decisions: what the seed governs (world layout only, or every roll including drops and AI — full determinism enables perfect verification but lets memorization replace adaptation), seed visibility and entry (buried in files versus shareable strings versus daily-automatic), and leaderboard segregation — seeded and unseeded records must never share a board, because they measure different sports. Pitfall: seed-knowledge collapse — when a known seed's optimal route is documented, replaying it tests transcription, not play; daily seeds solve this with expiration (the answer key publishes after everyone's attempt), and evergreen seeded modes need enough hidden state or execution demand that knowing the map doesn't mean owning the run.

SEEN IN

VIEW “SEED-BASED RANDOMNESS” IN THE MAP ▶