Create establishes the restaurant and its creation choices. Edit changes its ongoing profile and supporting locations. Creation requires a global administrator1; ongoing configuration is available to that administrator or the restaurant's owner2.
1. Open the right restaurant#
Use /restaurant or F7. The left restaurant list selects the current business; its + action opens Create Restaurant. Check the current restaurant name before editing a shared server.
Create Restaurant with profile, interaction, locations, starter and map choices.
2. Fill in the profile#
| Field | What to enter | What it changes |
|---|---|---|
| Restaurant Name | A clear name such as Copper Spoon | Staff and restaurant records use this display name |
| Interaction Type | Target or TextUI | How supported published fixed points are opened |
| Map Blip | On when you want a public map marker | Marker visibility; it does not place a kitchen |
| Map Blip Coordinates | The intended marker location | Independent from Management, Packaging and Menu locations |
| Management Point | Optional management access position | A convenient world entry to authorized management |
| Packaging Point | Staff packaging/storage position | Where staff access those features |
| Menu Locations | One or more named customer locations | Public menu, order view and customer pickup admission |
| Restaurant Template | Manual or a supported starter | Creation-time kitchen authoring mode/defaults |
| Map Preset | A matching installed map or none | Creation-time recipe/location seeds |
Use a location's picker to inspect it in the actual world. A coordinate that parses correctly can still be inside a wall or under a floor. Locations explains the three access points; Templates and Maps explains the creation choices.
3. Save the new restaurant#
Use the creation form's Save action. Resolve any validation error while the form is still available. Once the restaurant exists, open its Staff Roster and Kitchen pages to finish the setup.
Creation is not proof of a working live kitchen. Recipes, active staff, placement, enabled state and publication still need review. Follow Your First Working Restaurant for that sequence.
4. Edit an existing restaurant#
Select it and open Edit in the management rail. Change only the intended fields. Use the named location chips to edit existing menu locations or + to add another. A location dialog buffers its own edits until its Save action is accepted.
Existing restaurant Edit view with profile settings, locations, enabled state and draft actions.
Apply open forms, then save draft3 and publish4. The published profile stays active while you edit another draft. Names, images and profile/access changes generally preserve unchanged kitchen preparation; recipe structure, timing or placement changes can reset temporary work.
Expected result#
After publication, the restaurant's public blip and world entry points reflect the published profile. Authorized staff and owners see the appropriate destinations. A saved Draft row by itself means a publication may still be needed.
Common mistakes#
- A blip is visible but there is no menu: add and publish a Menu Location; the blip is only a marker.
- A different building has no usable stations: remove the incorrect map assumption and place the correct draft locations.
- An administrator cannot cook: add actual active staff membership and publish it.
- A form was filled but nothing changed: accept the form, then save the whole restaurant draft and publish it.
Continue with Staff, Locations and Save and Publish.
Footnotes
-
A player with the server ACE capability configured for Restaurant management. Read the definition. ↩
-
The restaurant role with configuration and business-finance authority. Read the definition. ↩
-
The action that validates and persists the restaurant draft without activating it for gameplay. Read the definition. ↩
-
The action that validates and activates the latest saved restaurant configuration. Read the definition. ↩