How to update an add-on you already shared

Change your add-on without leaving players with two copies or a pack that refuses to import.

Keep the UUIDs, raise the version

The header UUID identifies the pack. To publish a new version of the same add-on, keep every UUID as it is and raise version in the header and in the module, for example from [1, 0, 0] to [1, 0, 1]. Minecraft then replaces the old pack.

Update the dependency too

If the behavior pack depends on the resource pack, the version inside dependencies should match the new resource pack version.

New UUIDs mean a new add-on

Changing the UUIDs makes Minecraft treat the file as a different pack. Players end up with both in their list, and worlds keep using the old one.

Do not rename identifiers

Worlds store items and blocks by identifier. If ab:ruby becomes ab:red_gem, every ruby already in a chest or placed in the world is lost. Add new things freely; rename nothing that players already have.

In the maker

Templates downloaded from the template pages keep the same UUIDs every time, so a newer download updates the older one. A project in the maker keeps its UUIDs for as long as you keep the project; use Save project to keep the file and Open project to continue later.

More guides

More from 9Minecraft