Consumption

Use a real finished inventory product from its owned slot. Eating/drinking does not require current staff membership, restaurant proximity or an enabled kitchen. It requires valid product metadata and an enabled item usage profile¹.

1. Hold the product#

Choose Use on the finished item in inventory. Restaurant verifies its slot, character and metadata, then prepares the held prop/animation. Raw material packets and unknown usage keys are not edible products.

Kitchen work, delivery carry and consumption reserve incompatible hands. Put away the other activity before beginning. Vehicle/death/character/world changes and relevant provider stops can close consumption safely.

The first inventory Use prepares holding; it does not automatically consume the whole item. Follow the current on-screen primary/put-away controls. The defaults use E for primary and X for putting away, as configured in item usage settings.

2. Eat or drink a portion#

Use the primary action to open the container or eat or drink one portion. Wait for the progress to finish. After a successful use, the portion count decreases and its configured effects apply.

Putting the item away does not consume it. You can cancel during use only when the profile allows it. An interrupted use before consumption leaves the portion intact. If an error appears, check the item before another attempt.

Understand saved portions#

A product can have several bites or sips. The first successful use saves its total and remaining portions. Each later use reduces the remaining amount. Finishing the last portion removes that product or reduces the batch by one product.

Passing a partly used product through supported inventory transfers does not refill it. Packaging, bag opening and storage preserve usage metadata. Saved totals remain after later portion-config changes; previously unused products follow the current profile when their counter is first created.

Donut batches keep their product details in order. Splitting/package selection moves the active partial counter with the first selected product rather than duplicating it across both resulting stacks.

Pizza boxes and slices#

The Pizza box remains one logical product. Opening records/reuses its portion state and switches the held view to a slice. Eating reduces remaining slices and returns to the box when more remain.

Putting away a held slice first returns to the box; putting away the box closes usage. Reopening an already recorded box selects a remaining slice without replenishing the count. A visual view change is not another inventory grant.

Effects and alcohol#

Portion profiles normally apply their full configured effect for each bite/sip. Profiles using per-container scaling divide the configured effect across portions. Check the installed profile rather than assuming a food label defines hunger/thirst.

Drinking adds alcohol according to the drink's configured ingredients. The level falls over time and can change walking and screen effects. Non-alcoholic ingredients add no alcohol. Follow the level-change notifications.

When Use fails#

Check the item's usage profile, saved details and inventory slot. Put away other held items and stop any conflicting activity. An unknown or disabled profile can prevent eating while still allowing storage. If an item change or effect fails, check the reported error before using another portion.

Follow Inventory and Consumption Problems or Item Usage Profiles. Existing item identity should be inspected before changing a material's profile selection, because that selection affects newly produced stock.