Skip to content

Rules and review ​

Inventery is a lot like an app store: very free, and strict only where it protects the basics of being a person in a shared world. Here's the whole list, and why each rule exists.

The hard rules ​

1. Leave always works. It's "Leave {your plot}", the first item of the settings menu, whose button is always on screen in every plot; the room performs it at once, whatever your plot is doing. Why: it's what makes everything else safe to allow: strict cameras, full-screen menus, horror, start countdowns. No one is ever stuck.

2. The trusted layer is ours. The settings button (and its Leave), chat, the protection ring and the start countdown, the "keep your items?" prompt, "Typing to {plot}" and real nametags are drawn over everything, and reserved controls never reach your plot. Why: a plot can draw anything, including a fake sign-in or a fake player. Players need a few things they can always believe.

3. Lasting harm needs consent. Only a plot that doesn't stash items can touch a player's real items or body, and only after they choose to keep their items in a prompt we draw. Harm happens only inside your plot, and deaths are soft by default. Why: walking into someone's plot shouldn't cost you anything you didn't agree to. Stashing plots never ask, because they never impose.

4. No secrets, no device, no money. You get a per-plot player id and a display name; no accounts, tokens, clipboard, notifications, camera, microphone, location, network or real-money purchases. Why: the sandbox has no way to reach them, so nothing can go wrong there. (Spending Nimgots through a base-drawn purchase sheet is Later.)

5. Report and block. Players can report a plot, a player or a piece of content, and block a plot (it then shows as plain colours and is silent for them). Why: user-generated worlds need a way for people to say no.

Things that are your choice ​

Everything else. Your game's rules, art, camera, controls, UI and difficulty. Which of the base game's rules run in your plot (all of them by default; a runtime can turn categories off). Killing players (inside), full-screen effects, flashes and loud sounds (rated and moderated, not capped), your own economy and progression in your storage.

Review ​

WhenWhat happens
Publishingautomatic checks: text through the chat filter, images, your module's imports; you declare a content rating and tags
Livereports, moderation, and replay of reported sessions (your code is deterministic, so sessions replay exactly)
If neededan admin can stop a plot (it freezes, like a crash) or take content down

Age ratings: players' settings hide plots rated above them. Chat in your plot always goes through the base chat filter, whatever UI draws it. Deleting an account removes that player's records from every plot's storage.

Be a good neighbour ​

  • Keep your own UI off the settings button (top left), the chat button (top right) and the top-centre ring (entry protection, the start countdown).
  • Put what matters in the scene, so your plot looks alive from outside.
  • Don't spin the CPU: over-budget plots are slowed, then suspended.