Appearance
Inventery for developers
Build games and content that live in a shared world. A plot is a piece of the Inventery world that runs your code. People see it from outside, walk in, and they're playing. Nobody installs or downloads anything.
These docs are for people (and agents) writing plot code: a Bedwars, a story dungeon, a shooter, a gravity platformer, an imported 3D level, or a few new blocks with a recipe.
Where things stand (2026-10-26). The plot runtime is being built on the
plot-runtimebranch. The runtime, the SDK, the harness and the protocol run headless: you can write, build, lint and run a plot on your machine. Plots also run in a real room process with plot hosting, part of the core game (src/plots/; the local plots dev stack, in a browser and in the iOS app's native plot UI). They aren't in the live world, staging or production. Every page marks what's built and what's planned (see the legend below).
Start here
- What you can build: the landscape, and nine kinds of game
- Quickstart: your first mod in about five minutes
- The mental model: the one page to read before writing real code
How these docs are organised
They follow the four kinds of documentation from Diátaxis: the quickstart is a tutorial (learn by doing), guides are how-tos (get a game built), concepts are explanation (why it works this way), and the reference is lookup (every call and type). Each page says what you'll learn first, and when you'll need it.
Status legend
| Label | Means |
|---|---|
| Built | In the SDK and the runtime on plot-runtime. You can build, lint and run it on your machine, headless and (where a page says so) in the plots dev stack. Not in the live world yet. |
| In progress | Being built now. The shape here is the decided one; small details may still move. |
| Planned | Decided (decision register), not built yet. |
| Later | Decided and deliberately deferred. |
Where these docs and the design docs disagree, the decision register wins.