# Check a Nexo item stack-size change before updating inventories

A stack-size change can affect storage and item handling even when the model looks unchanged. Compare new and existing copies before applying the change to items players already own.

## 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

1. Record the item ID, base material and existing stack size on your installed Minecraft and Nexo versions. Back up the item definition and a staging inventory containing representative copies.
2. Check the matching version tab in the component reference. Create a temporary item ID with the intended maximum stack size and no unrelated mechanics.
3. Obtain fresh test copies and combine or divide stacks in an ordinary inventory and a chest. Include one stack near the intended limit and one transfer through your normal shop or menu.
4. Compare the new test item with an old copy after a staging restart. Check the supported item-update behaviour before expecting stored copies to inherit the new component.

## Verify the result

Stacks should respect the intended limit without disappearing, duplicating or losing the Nexo identity. Shops and rewards should handle quantities that cross the new boundary correctly.

## If the result differs

If only a third-party menu behaves incorrectly, test normal inventory handling first and report the integration difference. If the component does not load, inspect version support rather than repeatedly regenerating the resource pack.

## Keep a recovery path

Restore the saved definition and test inventory checkpoint if the new limit is unsuitable. Do not force a mass inventory conversion while stack behaviour is uncertain; document any required migration separately.

## References and related help

Check the maintainer reference: [Nexo documentation](https://docs.nexomc.com/configuration/items/components).

Before changing live data, read [how to keep a completed recovery copy](https://help.cloudexa-hosting.com/books/game-hosting/page/back-up-game-files-before-making-changes). For startup errors, use [the log collection guide](https://help.cloudexa-hosting.com/books/game-hosting/page/find-minecraft-logs-and-send-useful-troubleshooting-details).