# Prepare an ItemsAdder content update with a stable ID inventory

A content update can rename or remove items that already exist in player storage. Build an ID inventory before merging a new pack so you can identify destructive changes.

## Check the installed content

ItemsAdder content uses namespaced identifiers for items and other assets. A definition, its generated resource pack and the copy downloaded by a player are different checkpoints. Keep content IDs stable and consult the documentation matching your ItemsAdder and Minecraft releases.

## Work through the change

1. Export the current content folder and list the namespaces and item IDs used by recipes, shops, rewards and placed objects. Include content supplied by third-party add-ons.
2. Compare the incoming pack in a separate directory. Mark removed IDs, reused IDs, changed asset paths and changes to persistent blocks or furniture rather than merging it over production.
3. Apply the update to a staging copy with representative old items, placed objects and containers. Generate its pack and inspect the first load errors before inviting testers.
4. Test old and new copies of selected items, crafting, placement and a clean restart. Record any migration method the pack author requires for your installed release.

## Verify the result

Existing content should retain its intended identity and behaviour after the update. Every removed or changed persistent ID should have a documented migration decision before the production maintenance window.

## If the result differs

If the pack loads but old items fail, inspect updater and migration behaviour. If a new ID reuses an old purpose, stop the merge; changing a texture alone cannot resolve conflicting persistent identities.

## Keep a recovery path

Recover the previous content, generated pack and affected world or inventory state from the same checkpoint if the migration fails. Restoring only the plugin JAR can leave incompatible updated data behind.

## References and related help

Check the maintainer reference: [ItemsAdder documentation](https://wiki.itemsadder.com/plugin-usage/beginners/configs-and-resourcepack/).

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).