Why an add-on does not import or does not work
A checklist for the most common reasons, from the file itself to the world settings.
The file does not import
- It is not a valid archive or has no
manifest.jsonat the top of each pack. Drop it into the add-on file checker. - A pack with the same UUID and version is already installed. Minecraft skips it as a duplicate. Raise
versionin the manifest, or remove the old pack in Settings > Storage. - The game is older than the pack asks for in
min_engine_version. Update Minecraft.
It imports but nothing changes
- The packs are not activated in the world. Edit the world and check Behavior Packs and Resource Packs.
- Only one of the two packs is active. Custom items and blocks need both: the behavior pack defines them, the resource pack names and textures them.
- Another pack higher in the list changes the same vanilla file and wins.
Items are there but look wrong
- Black-and-magenta squares: the texture name in the item or block does not match an entry in
item_texture.jsonorterrain_texture.json, or the PNG is missing from the resource pack. - Names like
item.my:ruby: the resource pack is not active, or the name is missing fromtexts/en_US.lang. - Armor is invisible when worn: armor needs an
attachablefile in the resource pack. The item maker writes one.
Read what the game says
Turn on Settings > Creator > Enable Content Log GUI and Enable Content Log File. When a world loads, every file the game rejects is listed with the reason, for example a recipe that uses an item ID that does not exist. That message is the fastest way to the fix.
More guides
More from 9Minecraft
Bedrock CommandsEvery Bedrock command with generators, for your function packs.Bedrock WikiBlocks, items and mobs of Bedrock Edition.RecipesEvery vanilla crafting recipe, to see what yours will sit next to.Marketplace trackerWhat is new and popular on the Minecraft Marketplace.Bedrock SkinsSkins and skin packs for Bedrock Edition.Download add-onsReady-made add-ons for Minecraft Bedrock.