MineBrushAn add-on update is a small migration, not just a newer download.
The world, behavior pack and resource pack form a versioned system. Preserving the last working set makes failures reversible and gives the new version a fair test.
Archive the current world and pack files, read the new changelog, confirm matching behavior/resource versions, test the update on a copied world, then keep the rollback copy until the new version has saved and reopened successfully.
Why partial updates create confusing failures
Dependencies can point to a specific pack UUID and version. Updating only the behavior pack or only the resources can leave mechanics and visuals out of sync. Duplicate identifiers from older installs can also make it unclear which copy Minecraft selected.
Before you change the world
- Export the world and store it separately.
- Keep the last working behavior and resource pack files.
- Read breaking changes, dependencies and required engine version.
- Record the current active pack order.
Step-by-step workflow
- Import the complete new release set.
- Open a duplicate of the current world.
- Verify that the intended pack versions are active.
- Test custom items, entities, recipes and saved areas.
- Save and reopen; only then schedule the update for the main world.
Compatibility check
| CHECK | WHAT GOOD LOOKS LIKE | IF IT FAILS |
|---|---|---|
| Release set | All matching layers use the intended version. | Re-download the complete update from the official creator. |
| World copy | A restorable pre-update save exists. | Export before further testing. |
| Content test | Custom entities, blocks and items survive. | Roll back and report the exact regression. |
| Reopen | World saves and reloads cleanly. | Do not promote the update to the main save. |
When it does not work
If the new version fails, protect the evidence and the rollback route.
- Return to the archived world and last working pack set.
- Remove accidental duplicate versions only after confirming their identifiers.
- Reproduce the issue in a clean world if possible.
- Send the creator the exact game version, pack version and reproduction steps.
Never overwrite the only working pack set.
Archive the previous world and all related pack layers until the update has passed real play, save and reopen tests.
Frequently asked questions
Can I install the new .mcaddon over the old one?
Import may succeed, but duplicate or mismatched versions can still require cleanup and testing.
Why did the new pack remove custom items?
The update may contain breaking identifier or component changes; restore the backup and read the changelog.
How long should I keep the backup?
At least until the new version has survived normal play and multiple clean reloads.
First review pack layers, then use the diagnostic checklist if the update fails.
Official technical reference
The official manifest reference documents pack versions, minimum engine versions and dependencies. Read the official Minecraft Creator documentation ↗.
PLAYER QUESTIONS
Discussion
Include the exact edition, version and step when asking for help.