Make a Nexo consumable return the intended container

A consumable that returns a bowl or bottle needs both correct consumption and correct remainder behaviour. Test a small disposable stack before connecting it to a shop or quest reward.
Check the installed content
Nexo manages custom content through item definitions, resource-pack files and optional mechanics. A correct item identifier does not prove that the client received the matching pack. Follow the documentation for your installed build and keep its generated assets with the source definitions.
Work through the change
Write down when the item may be consumed, how many units it should use and which container should remain. Check the installed-version component examples for food, consumption and remainder support.
Create a separate staging item with the minimum required components. Avoid command rewards or extra mechanics until the basic consumption cycle works.
Consume one item from a single-item slot and then from a larger stack. Repeat with a nearly full inventory so you can observe how the returned container is handled.
Test after relogging and after an orderly staging restart. Compare fresh items with existing copies to identify updater behaviour rather than assuming the definition rewrites every stored item.
Verify the result
Each use should consume the intended amount and produce only the planned container and effect. Players should not receive an endlessly reusable reward or unexpected extra stack.
If the result differs
If the item displays correctly but cannot be used, inspect component compatibility and consumption conditions. If it works only with a fresh copy, review the supported update policy before replacing anything in production.
Keep a recovery path
Restore the previous consumable definition and remove the disposable item from test rewards. Keep a record of distributed test copies because configuration rollback cannot undo already applied effects or returned containers.
References and related help
Check the maintainer reference: Nexo documentation.
Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.