Skip to content

Ice Cream Setup

Set up Ice Cream stations, dependencies and a production check.

Ice Cream is served from a personal registered vehicle. One recipe can publish several spawn/return points under one access policy. The vehicle creator owns its preparations on either serving side.

Configure the vehicle service#

Add the ready Ice Cream recipe. Configure the allowed mobile access, named spawn/return locations and optional marker. Place the points with enough room for the vehicle, save and publish.

Use a working target and vehicle-key provider1, even if your fixed kitchen uses TextUI. Check both before testing the Ice Cream vehicle.

Settings and dependencies#

This preset belongs to a Template restaurant. Configure the Staff/Everyone policy and all spawn/return points. Mobile service requires a target provider and supported vehicle keys.

ChangeLocationApply the change
Labels, supported recipe fields and placementKitchen > RecipesApply the form, Save draft, then Publish
Supported future-product defaults0r-restaurant/config/products/icecream.luaRestart main; review existing saved copies before any supported upgrade
Models, camera and equipment positions0r-restaurant_assets/config/products/icecream.luaRestart assets during maintenance
Portions and hunger/thirst0r-restaurant/config/item_usage.luaRestart main; existing item details remain saved
Holding, eating and drinking appearance0r-restaurant/config/item_usage/visuals/icecream.luaRestart main; keep the item's presentation name matched
Alcohol and additional effects0r-restaurant/config/item_usage/effects.luaRestart main; saved ingredient details remain unchanged

Ready preparation supplies its configured ingredients rather than consuming ordinary custom-material packets. Check Product Defaults before editing files.

Capacity, timing and cleanup#

The delivered fill duration is 2 seconds. The mobile vehicle settings are in config/products/icecream.lua: vehicle.model, spawnRadius, returnRadius, servingDistance and maxServingSpeed. The delivered model is taco, with 3.5 m spawn radius, 5 m return radius, 3 m serving distance and maximum serving speed 0.15. Review both serving sides and all spawn/return points. Target and supported vehicle keys are required; changing the restaurant to TextUI does not replace them.

Change supported saved durations through the recipe form, then Save draft and Publish. For source defaults that are copied into a recipe, editing the file and restarting does not rewrite existing copies. Use a supported explicit upgrade when required, review its changed placement and publish it. Before planned restart or kitchen-changing publication, finish temporary work; see Shared Work.

Verify the installation#

  1. Save and publish a complete enabled recipe.
  2. Join with a character allowed to use it under the selected mobile access policy.
  3. Complete one preparation using Ice Cream Preparation.
  4. Check the finished item, its quantity, image and saved contents in inventory. Use a configured consumption profile to check eating or drinking.

For missing stations or placement problems, use Kitchen Problems. For a failed transfer, keep the error and check Inventory Problems. Review Shared Work before a restart or kitchen change.

Detailed preparation steps

1. Spawn and park safely#

Continue at 1. Spawn and park safely.

2. Choose container and flavor#

Continue at 2. Choose container and flavor.

3. Add sauces or toppings#

Continue at 3. Add sauces or toppings.

4. Collect the finished serving#

Continue at 4. Collect the finished serving.

Undo, leave and reset#

Continue at Undo, leave and reset.

Return and cleanup#

Continue at Return and cleanup.

Footnotes

  1. An installed framework, inventory or interaction system used by Restaurant. Read the definition. ↩