The World File
A World file is the contract between this system and a setting. It is the answer to "create a world based on GLASS": one file that names the setting, binds it to the engine, and states — honestly — whether it changed anything.
What a world binds
Every World file carries the setting's identity layer: the setting_name, the tagline, the fiction (description), the name of the surveillance lattice (surveillance_name — GLASS in the home setting, rename it to port), the two currencies (legal_currency / street_currency with their premium), the starting stake a new character receives, and which optional_rules modules the world runs.
The defaults are the GLASS core. A blank World file already runs 2d12, the fixed DC ladder, the standard HP and XP tables, ES/CC, and a 500 ES / 150 CC starting stake. You only fill in what differs.
What a world does NOT bind
The World file does not contain rules, factions, NPCs, or locations. Rules stay in GM Instructions; factions and people are content files; places are Location files. The World file is the small, load-bearing document that says which rules load and what names they use — not a bucket for everything about the setting. If you find yourself putting a rule in a World file, it belongs in an instruction; if you find yourself writing a faction's history in it, that belongs in its own file.
The porting protocol
The World file operationalizes the porting chapter of Extending the Rules:
- Fiction swap. New
setting_name, renamedsurveillance_nameand currencies, newdescription. Everything structural stays. This is the weekend port — the World file is finished in an afternoon, and the content work (locations, factions, gear reskin) follows at content speed. - Optional modules. Turn
optional_ruleson or off per world. Armor degradation is the current switch; new optional subsystems should register here as a short slug, so a game master can see a world's module loadout in one glance. - A fork, declared. If the math changes — different dice, a different XP table, different HP — write it in
system_notes, loudly. The home world's note reads "Runs the GLASS core exactly as written"; a fork's note should be at least as specific about what it breaks. A fork that hides in a World file is the worst of both worlds: content built for one engine read by a game master running another.
Working with multiple worlds
Worlds are files, so a project can hold several — the home Megacity plus any number of ports and forks. Content stays shared: a weapon, a talent, or a hostile file belongs to the system, not to one world, and any world can cite it. What is world-specific gets named for its world or filed under it. When a game start runs, it runs in one world; the World file it points at decides which names the lattice and the currencies answer to.