Shipping It, or Not

Three different things get called publishing, and only one of them is.

Using it in your own game. The common case. Nothing to publish, nothing to decide. Build your world in your project and play it.

Keeping it private. Also common, also correct. Mature or heavy material that belongs at your table and nowhere else stays there. Private is a real end state, not an unfinished one, and nobody should make you feel otherwise.

Sharing it so others build on it. The rare case, and a deliberate one.

The checklist that matters either way

Setup/Sharing What You Made carries the full checklist and stays current — read it there rather than here.

Before you hand it to anybody

Run the workspace check. Every failure there is something the server would reject at push, so a green run is the floor rather than the goal.

Then open @Missing file and actually do it. The failures that matter at this stage are not schema failures — they are a mechanic nothing names, a field nothing reads, and a tab that renders empty on the one file a stranger will open first.

@Missing file covers the rest of the handover, including what a clone does and does not carry.

Releases

A private release is numbered, immutable, and a rollback point you will be glad of later. Take them freely — there is no cost and no audience.

A release snapshots the server state, so unpushed local edits are not in it. Push first if you meant to include them; this catches everybody once.

Public is a separate decision. It puts the project in a catalog strangers clone from, and the release your handbooks ship with is tied to it permanently. Nobody should do it by accident, and nobody should be talked into it — including by this book.