Appearance
Building with an agent
You'll learn: how creation with an AI agent will work in the world, and what to give an agent writing mods today.
Soft-Bot (Planned: design only)
Creation happens in the world. Soft-Bot, an NPC, stands for a real agent harness running in your own cloud container, never on your device.
- The container holds your source as a versioned repo, the SDK and the harness.
- The agent builds, tests headless, looks at onlooker renders, uploads artifacts and updates your draft.
- The room hot-swaps your draft lobby: you see changes where you stand.
- You publish when it's right.
- AI usage is paid by the creator, probably with a resource bought with Nimgots.
Writing mods with an agent today
The platform was designed for agents: a small boundary that fits in context, full types, refusals that name the rule and the fix, and a lint for the mistakes that are easy to make.
Give your agent:
- llms.txt: a one-page cheat sheet of the rules, the shape of a package, and the common calls.
plot/sdk/AGENTS.md: the generated reference (every hook, call, type, refusal rule and manifest field).plot/NAMING.mdexplains the API's names, if an older name turns up somewhere.plot/sdk/host.d.ts: the types, with a doc comment on every call.- The examples: four small plots that build, lint and run.
And a loop: edit, then
sh
node plot/sdk/lint.mjs <dir> && node plot/sdk/build.mjs <dir> && node docs/developers/examples/run.mjs <dir>Tips that make agents effective here:
- Ask for a runtime or a mod explicitly; it changes what's allowed. A team game can often be a mod on an existing runtime (Team Minigame), as Bedwars and Spleef are.
- Tell it the base game already runs inside the plot (breaking and placing, two-part beds and doors, PvP, drops, pickup, hunger): it should filter those with hooks, not rebuild them.
- Ask it to keep state in
storage(ordefineLobbyGame), never only in variables. - Ask it to check what onlookers will see: "what's in the scene?"
- Paste refusals back verbatim; they say what to do.