Building a Storage Entry & the Looting Layer
A Storage file is how a location keeps things a party can find. It is a stationary container — a pantry, a crate, a locker, a cargo pod — with a typed inventory, an owner, a lock, and a sheet that does its own accounting so the Master never has to hold a room's loot in their head. Building one is the same reference craft as a character's inventory, with the container pinned to a place on the map.
The type, in one line
A Storage entry is an object with an inventory and an owner, tied to a Location, that lives on that map as a token. It reaches outward the way a character does — rows point at Equipment or Ammunition files, a location points at a Location, an owner points at a Character. You never paste the items' stats in; you point at real files.
The fields you write by hand
storageType— the stage word for what it is:Pantry | Crate | Cabinet | Locker | Chest | Shelf | Ammo Box | Medkit | Safe | Cargo Container | Cryo Pod | Fuel Tank | Trash Bin | Rack | Other. It is an enum because the Master reads it aloud and improvises from the object, not from a mood.location→ a real Location file.owner→ a real Character file (or, for an owned-but-abandoned crate, a faction's face);number— the running identifier for the party's log.locked+lockRule— whether it bars strangers, and the rule for opening it unowned. The default rule rides the system's own engine: an opener who is not the owner rollsLockpicking — 4d6 vs Agility (AG)at the Master's difficulty. Setlockedtruthfully; aMedkitbehind quarantine is the load-bearing wait in a horror scene.inventory— rows of(item, quantity), eachitema reference to a real Equipment or Ammunition file, exactly like a character's inventory.quantityis a number ≥ 1. One row, one real object — never prose describing "a bundle of supplies" where a typed entry belongs.inventorization— the Master's running log of what the container holds and every transfer in or out. This is where a raid that opened last session still reads true three sessions later. It is prose on purpose: it is a journal, not data.
The fields the sheet derives — never hand-type
Computed fields do the container's arithmetic, and writing to them is rejected. Change the inputs instead:
| Computed | What it is | You change… |
|---|---|---|
displayName | the autonomous Type_Location_Owner_Number name | storageType, the linked location/owner, number |
summary | the auto-updated contents list | inventory rows / quantities |
totalWeight | the sum of every item × its own weight | the weight on the gear, or the rows |
itemCount | how many distinct rows | the inventory rows |
displayName is the file's fingerprint — Pantry_NeonWalk_Unit_Echo_001. Keep name (the file's name) and number consistent so a token's label and the sheet's name agree; the computed name is the truth the map shows.
Wire the container to the world
Two links make it real:
- On the map of its
location, place a token and link it to the Storage file. The party seesPantry_NeonWalk_Unit_Echo_001as something they can click open — that is the whole point of the type. - Seed honest contents against the location's fiction. Price a container against the room it sits in and the
GENREVALUEeconomy (see Skills, Crafting & the Market): a gutted ruin's crate holds salvage, a quarantine medkit holds medicine that someone in the sector would trade, kill, or guard for. A container detached from its location is a loot table wearing a room's clothes — the same silent break the system guards against elsewhere.
Worked entry
{
"name": "Medkit_QuarantineWing_DrOne_012",
"storageType": "Medkit",
"location": "quarantine-wing",
"owner": "dr-one",
"number": "012",
"locked": true,
"inventory": [
{ "item": "equipment/anti-hemorrhagic", "quantity": 2 },
{ "item": "ammunition/9x19mm-parabellum", "quantity": 40 }
],
"inventorization": "## Initial\n- Anti-hemorrhagic ×2\n- 9mm ×40\n## Raid (night 3)\n- −1 anti-hemorrhagic → took to Dr. Voss"
}
displayName resolves to Medkit_Quarantine Wing_Dr One_012, summary reads the inventory, and totalWeight sums the real gear weights. The only number you typed by hand is the truth about who owned it.
Checklist
-
storageTypeis set to a stage word from the enum, not a freeform label. -
location→ a real Location file,owner→ a real Character file,numberset. -
inventoryrows reference existing Equipment/Ammunition files (plain slug orequipment/<slug>) — never prose. -
locked/lockRulereflect whether the container bars strangers and the AG-opening rule it falls under. -
displayName,summary,totalWeight,itemCountare left computed — you edit inputs, not derived numbers. -
inventorizationis a live transfer log, updated as loot moves (one ledger at a time on each side). - A linked token sits on the
location's map, labeled by the computeddisplayName. - Contents are priced and placed against the location's fiction and
GENREVALUEeconomy.