Place spawn and return locations for Hotdog, Sandwich or Ice Cream service. Players then create their own mobile instance1: a cart or vehicle that keeps their food while they use it.
Configure the mobile recipe#
- Add the product's ready recipe in a template restaurant.
- Open its mobile settings.
- Choose staff or everyone access as appropriate.
- Add named spawn/return points and place their coordinates/heading.
- Review the optional spawn-point map marker.
- Save draft and Publish the complete enabled recipe.
Choose Everyone if non-staff players should be able to spawn their own cart or vehicle. They cannot take over another player's preparation or view private staff details. Place the required spawn and return points before publishing.
Required providers#
Mobile interactions require a working target interaction2 provider even when fixed restaurant points use TextUI. Ice Cream vehicles also require the supported vehicle-key bridge. Verify OneSync and room at the spawn location.
Use Providers if targets or vehicle keys fail. Spawn and return the vehicle through Restaurant's own interactions.
Administrator check before opening service#
After publication, use a character allowed by Staff/Everyone to spawn one instance, operate one serving side, move/park a cart where applicable and return the instance normally. Confirm keys and serving restrictions on Ice Cream. Repeat the access check with a non-staff character when the intended policy is Staff. Restarts remove unfinished mobile work; finished inventory products keep their saved contents.
Spawn, operate and return#
Use the published spawn interaction with an allowed character. Wait for your cart or vehicle and any keys, then open its serving interaction. Follow the product guide:
- Hotdog: independent grill slots, cooked sausage, assembly and parking.
- Sandwich: bread/filling assembly and parked sandwiches.
- Ice Cream: timed filling and separate serving sides on the owned vehicle.
Other players can see your food, but only you can continue preparation on your personal cart or vehicle. Another employee can continue shared fixed-station work under its separate rules.
Move a push cart#
Use the movement action on a Hotdog or Sandwich cart. Follow the displayed controls and finish the move. Your food stays on the same cart.
Moving a cart leaves its saved spawn point unchanged. After a restart or character departure, use a configured spawn point again.
Leave versus discard#
Escape leaves the operator view and retains accepted work under the product rules. Carts try to park accepted assembly when space permits; a full parking area retains the active assembly while allowing exit. X discard resets the owned active preparation after server acceptance, not every parked product or unrelated grill slot.
On Ice Cream vehicles, Escape leaves the serving and remaining fill time on that side. X resets that side only. Working on one cart or vehicle does not extend the inactivity time for another one.
Return and removal#
Return your cart or vehicle through its return interaction. Ice Cream vehicles remain after player death or a publication that leaves the kitchen unchanged. Leaving the server, changing character, returning the vehicle or resetting the kitchen removes it. Hotdog and Sandwich carts also disappear when their owner leaves.
If the cart or vehicle disappears, its serving interactions close. A restart clears unfinished preparation. Finished products already in inventory keep their saved contents.
If a cart or vehicle does not appear, check access, spawn location, free space, targets and keys, then read the server error. If serving fails, check inventory before retrying. See Kitchen Problems and Inventory Problems.
Footnotes
-
One player-owned serving cart or vehicle created through a published mobile recipe. Read the definition. ↩
-
A selectable world option provided by a supported target system. Read the definition. ↩