Wiki 9Minecraft Wiki 9Minecraft

Bedrock add-ons

The Bedrock way of changing the game: behaviour packs and resource packs together.

6Tools
5Reference pages
4Things to get right

Bedrock splits the job in two. A resource pack carries the look; a behaviour pack carries the rules. Most add-ons ship both, tied together by a manifest with a UUID for each.

Four things to get right first

Two manifests, two UUIDs

Each pack needs its own manifest.json with a fresh UUID. Reusing a UUID from another pack makes the game load one and silently ignore the other.

Version arrays, not version strings

Bedrock manifests want [1, 0, 0], not "1.0.0". The wrong shape means the pack simply does not appear in the list.

Minimum engine version matters

min_engine_version decides which features you may use. Set it too low and new components are ignored; too high and older devices cannot open it.

Test on a real device, not just the editor

Bedrock runs on phones, consoles and Windows with different limits. A pack that loads on a PC can run out of memory on a phone.

Tools that do the work

Reference, straight from the game files

Read out of the game with Mojang’s own data generator, so it matches the version exactly.

Other things you can make