Minecraft Bedrock Add-on Troubleshooting: Imports, Scripts and Textures

Separate import, activation and execution

An import success message only tells you Minecraft accepted a container. A behavior pack must also be active on the world, its dependencies must be compatible, and the intended gameplay trigger must run. A skin pack instead belongs in the Dressing Room. Check the file format before troubleshooting a missing ability.

Check the real manifest

Inspect every manifest.json in the download. Read header.min_engine_version, modules and dependencies. A script module points to an entry file and can depend on @minecraft/server. The generated version is evidence about a requirement, not proof that every device or future release supports your mechanic.

Paired behavior/resource packs must be enabled together when present. An mcaddon can contain more than one pack; a single mcpack normally imports one. Follow the generated README instead of renaming extensions at random.

Symptoms and next checks

• ▸Pack absent: confirm the file opened with Minecraft and your device supports external pack imports. Console file workflows differ from mobile and Windows.
• ▸Pack listed but no effect: activate it on the copied world, check engine/API versions and use the README's documented trigger.
• ▸Ability works but item is invisible: inspect the resource pack, texture references and priority relative to other packs.
• ▸World behaves differently with other add-ons: test this pack alone, then reintroduce others individually to identify a conflict.
• ▸Import or script error: preserve the exact message, manifest and files; report the target version and device.

A reliable test record

Use a new or copied world and record the output name, prompt, minimum manifest version, actual game version and action you performed. Test a simple successful trigger before a complex scenario. If a generator refuses the request, adjust the request rather than assuming a partial fallback implements the missing behavior.