Skip to content

Drafts, Templates and Publishing

Explain form changes, saved drafts and published restaurant settings.

Form changes#

Values still being edited inside an open form, before its confirmation action applies them.

For example, typing Red Pepper does not create a material row until Add material is accepted. Cancelling the form discards those unconfirmed edits. See confirming the material.

Local draft#

The restaurant configuration currently being edited in the panel, including applied but unsaved changes.

Switching editor pages retains this shared draft. Save draft persists it on the server. See saving and publication.

Save draft#

The action that validates and persists the restaurant draft without activating it for gameplay.

A successful save can leave Draft rows waiting for publication. The currently published kitchen continues running. See saving the example.

Publish#

The action that validates and activates the latest saved restaurant configuration.

Publication covers the whole saved restaurant setup, including other pending changes. A kitchen change can reset temporary production. See publishing the example.

Published configuration#

The saved restaurant setup currently used by gameplay.

A newer draft can exist alongside it. World interactions keep using this published configuration until another publication succeeds. See Save and Publish.

Record status#

A row label showing how its definition relates to the published setup or whether it needs recovery.

Published means this row matches its published definition; it does not mean all restaurant changes are saved. Draft, Incompatible and Disabled need their own checks. See record status.

Starter template#

A creation-time setup that seeds a restaurant with ready recipes and their shared definitions.

A starter gives you editable copies, not automatic world placement for every map. Later edits do not rewrite the reusable starter. See Templates and Maps.

Map preset#

A set of predefined locations for a particular installed map.

It can seed matching recipes and empty management/menu locations during creation. It does not install the MLO or building. See map setup.

Template upgrade#

Updating a saved recipe with the latest preset definition.

Review the affected recipes and their placements, then save and publish. Startup does not automatically rewrite saved restaurants. See Safe Updates.

Revision#

A change marker identifying the data shown in the panel.

If another person changes the same data, your panel may show outdated data. Refresh and review their changes before trying to save again. See Save and Publish.

Published snapshot#

The persisted restaurant configuration captured by a successful publication.

It preserves the published recipe and placement data independently from later draft edits. A database backup must include it with the related restaurant and business data. See Backups.