Minecraft Bedrock Addons

A Java mod injects new code into the game. It can add genuinely new systems — machines that process items, dimensions with their own physics, mobs with complex AI written from scratch.

A Bedrock addon works within a system Mojang provides. Behaviour packs change how existing entities act and can define new ones from existing building blocks; resource packs change how things look. Recent versions added a scripting API that widens what is possible, but the ceiling is still far lower than Java's.

The practical consequence: an addon can give you a new mob, retexture the world, change mob drops or add a custom item. It cannot give you the large technical mods that define modded Java Minecraft. If you specifically want those, you need Java Edition, and no addon will substitute.

On Windows and mobile the process is the same and takes about ten seconds: download the .mcaddon or .mcpack file, then open it. The operating system hands it to Minecraft, Minecraft imports it, and you get a confirmation message in-game.

If tapping the file does nothing on Android, use a file manager to locate the download and open it from there — some browsers hand off downloads badly. On iOS, use the share sheet and choose 'Copy to Minecraft'.

Once imported, the pack lives in your global content library. You still have to apply it to a world: edit the world, open Behaviour Packs or Resource Packs, and activate it. Importing alone changes nothing, which is where most 'it did not work' reports come from.

Xbox, PlayStation and Switch do not let you open downloaded files, so the direct method is unavailable. The supported route is the in-game Marketplace, where content is paid and curated.

There is a workaround: Realms. If you apply an addon to a world on a PC or phone and upload that world to a Realm, console players joining that Realm get the addon's content because it travels with the world. It is legitimate, it works, and it requires someone in the group to own a non-console copy.

Anything else you read about console sideloading is either out of date or describes something Mojang has since closed.

Many addons rely on features Mojang still classes as experimental. If an addon imports cleanly, activates without error, and then simply does nothing in-game, this toggle is almost always why.

Open the world's settings, scroll to the Experiments section, and enable the relevant toggles before generating the world. Enabling them marks the world as experimental permanently, which disables achievements for that world — an annoyance worth knowing about before you commit a survival save to it.

Turning experiments on for an existing world is possible but one-way. Copy the world first if you care about it.

MCPEDL is the largest independent library and where most free Bedrock content ends up. Quality varies enormously and the site is heavy with advertising, so be deliberate about which download button you click.

CurseForge has a Bedrock section that is smaller but better moderated. The in-game Marketplace is paid, but content there is reviewed and guaranteed to work on your version.

Whichever source you use, check the Minecraft version the addon targets. Bedrock updates frequently and addons break more often than Java mods do, because the underlying data formats change between releases.

Almost every addon is really one or both of two components, and knowing which is which explains most of the confusing behaviour people report.

A resource pack changes appearance only — textures, models, sounds, UI. It is purely cosmetic, it is safe to add and remove at any time, and it never touches your world data. If a pack promises new visuals and nothing else, this is all it is.

A behaviour pack changes logic — what entities do, what drops from what, how items work, and with the scripting API, a good deal more. Behaviour packs write into your world. Removing one after you have played with it can leave entities that no longer have definitions, which manifests as invisible mobs or items that do nothing.

A .mcaddon file is simply a container holding both, so that opening one file installs the matched pair. That is the only real difference between .mcaddon and .mcpack — the latter holds a single pack.

When two packs change the same thing, the one higher in the list wins. This is the explanation for the very common complaint that a pack 'stopped working' after installing a second one.

In the world's pack settings you can drag active packs up and down. The order is per-world, not global, so a pack that behaves in one world can appear broken in another purely because of where it sits in the stack.

The practical approach is to activate packs one at a time and check each works before adding the next. When something breaks, you know which addition caused it, and reordering is usually the entire fix.

Because Bedrock addons are data rather than compiled code, editing one is far easier than editing a Java mod. A behaviour pack is a folder of JSON files describing entities, recipes and loot tables.

That means you can change a mob's health, adjust what a block drops, or retexture something by editing a text file and re-zipping the folder. No compiler, no Java, no build step.

Microsoft publishes full documentation for the format, and the starter templates they provide are a genuinely reasonable way to learn. If you have a child who wants to make something in Minecraft, this is a considerably gentler entry point than Java modding.

The ceiling is real, though. You are composing behaviours from a vocabulary Mojang defined. When you want something outside that vocabulary, there is no escape hatch.

Bedrock updates more often than Java and changes its internal data formats more aggressively. Addons therefore break more often, and usually all at once when a new version lands.

The most common failure after an update is a format version mismatch. Every behaviour pack declares which format version it targets, and when Mojang deprecates one, packs targeting it stop loading. There is nothing you can do from your side except wait for the author to republish.

This is a genuine argument for keeping the Marketplace in mind for anything you rely on. Marketplace content is tested against each release before it ships; community addons are updated whenever the author gets to it, which may be never.

If a favourite addon breaks and is not updated, the only durable option is to stay on an older Bedrock version — which the game will fight you on, because it updates automatically on most platforms.