Inventory, Images and Consumption Problems

Distinguish a missing PNG, a rejected recipe input, a failed item transfer and a denied Use action. Their visible symptoms can be similar while their owners differ.

Item appears with the wrong name or quantity#

Check all three shared provider definitions, non-stacking/unique settings and the actual Restaurant metadata. One physical packet can contain a measured logical amount; one finished batch can contain several products.

A 250 g packet shown as one physical entry is expected. Verify the logical material quantity/unit before concluding that 249 items disappeared. See Materials and Quantities.

Image is missing#

Confirm that the supplied PNG exists in the selected provider's image directory with exact filename/casing. A Material's Advanced Inventory image selects a local basename; it does not upload a file or accept a remote URL.

Check with a newly produced item after Save draft and Publish. Old stock retains saved presentation metadata. Stock QB inventory shows its fixed item artwork unless its installed UI supports per-item metadata images.

For Recipe and Supply selection images, check the image paths in config/operation_points.lua as well as the installed PNG files. Test the image in game. Follow Inventory Images.

Recipe says inputs are missing#

Inspect the logical material, restaurant origin, unit and available amount, not only the provider item name. Raw/custom materials and finished products have different roles. A ready preset generally supplies its configured ingredients rather than consuming ordinary packets.

Check that the published recipe, not a newer unsaved draft, expects the amounts you are testing. Do not rename an existing packet's metadata to force a match.

A product transfer fails#

If the message confirms that your inventory is full and the food is still waiting, make room and use its collection action again. For a stock transfer, check that the original stock or item is still available before retrying.

An uncertain outcome¹ means the item may have moved even though confirmation failed. Further collection is blocked to prevent duplicates. Check the actual inventory and transfer record before giving a replacement.

For partial multi-item stock/pickup operations, establish the complete original or intended inventory outcome before administrator resolution. Do not resolve a partially moved state as if all bags were delivered. See Business Recovery.

Use does nothing or is denied#

Check the item is a valid finished product with an enabled usage profile. Existing items retain their usage key; changing the Material selection affects newly produced stock. Unknown keys can remain storable while denying use.

For Ox, keep consume = 0 and the proper server export. For QB/custom, preserve unique metadata and pass the actual owned slot in the usable callback. Registering a second automatic consume callback can remove the item outside Restaurant's flow.

Check current hands, movement/vehicle restrictions, death/character state, provider readiness and model/animation loading. Kitchen staff status and restaurant activation are not requirements for an otherwise valid inventory consumption session.

Portions or effects seem wrong#

Saved portion totals persist across config edits. A partial product does not refill when transferred or opened from a bag. Per-bite effects and per-container scaling differ; inspect the active profile.

Food effects apply after the item is consumed. If an effect fails, check the configured effect and framework support before another attempt. Repeating the effect or replacing the item can give the player an extra benefit. Use Usage Profiles.

For support, include the provider/version, actual slot and safe item metadata, operation error and whether the item appeared/changed. Avoid sharing unrelated personal inventory or credentials.

Check after correcting item setup#

Reload the selected inventory's item definitions through its normal maintenance procedure, start assets before main, and test one newly produced item with enough capacity. Check its full saved contents, image, use, remaining portions and final removal. Do not alter existing item metadata to make a broken registration pass.