Your addon worked yesterday and broke after the Minecraft update
Nothing about the file changed. What changed is the game underneath it. This page explains the three things a Bedrock update actually breaks — and which of them you can fix yourself in under a minute.
The short version: the pack still imports and still activates. It just does nothing, because the scripts inside it no longer run. In most cases the fix is one toggle — Beta APIs — and in the rest you need the build of the addon made for your version of the game.
Why an update breaks a pack that never changed
A Bedrock addon is not a program that runs on top of Minecraft. It is a bundle of descriptions — blocks, entities, recipes, textures — that the game reads and executes itself. So when the game changes how it reads them, a pack that was correct last week can become unreadable this week, without a single byte of it changing.
Three things change on a game update, and they fail in visibly different ways:
- The minimum version the pack declares. Every pack states the oldest game version it is built for. Update the game and old packs keep working; it is the opposite direction that hurts — a pack built for a newer version simply will not load on an older game.
- The scripting API. Addons with custom logic use Minecraft's script modules, and those are versioned separately from the game. When the game moves to a newer module, packs pinned to the old one stop executing — silently.
- The experimental toggles. Features move in and out of the "Experiments" list between releases. A pack that relied on one that got renamed or removed goes quiet.
Which of the three is yours — a 30-second triage
Before you start changing settings, find out which failure you actually have. The symptoms are distinct enough to tell apart:
| What you see | What it is | Where to go |
|---|---|---|
| Pack activates. Textures and blocks look right. Custom items, mobs or commands do nothing. | Scripts are not running | One toggle fixes it |
| Pack activates. Absolutely nothing appears — no blocks, no mobs, no menu entries. | Wrong build for your version | How version targeting works |
| Pack refuses to appear in the Available list at all, or errors on import. | Not a version problem | Import troubleshooting |
Those two linked pages go deep with the actual numbers — how many packs need the toggle, how the catalogue spreads across game versions. This page stays on the part they do not cover: what to do when the trigger was an update, and which direction the incompatibility runs.
The rule that decides everything: which direction the gap runs
Version incompatibility in Bedrock is not symmetric, and almost every wasted hour of troubleshooting comes from not knowing that.
A newer game runs older packs. An older game does not run newer packs. A pack built for 1.16 will almost certainly still work on 1.21 — the format it declares is a floor, not a target. A pack built for 1.26 on a 1.21 game will not load, and no toggle, reinstall or repair changes that.
So the moment you know your own version, you know which fixes are even possible:
- You updated the game and the addon is older than it. The update is almost never the real cause. Look at the scripting toggle first — that is the failure an update actually triggers.
- You updated the addon and it is newer than your game. Nothing to configure. Update Minecraft from your store, or take an older build of the same addon.
To read your own version: Settings → About in Minecraft. You only need the first two parts — 1.21, 1.20 and so on.
When the addon needs a newer game than you have
The one case you cannot work around from your side, and the one worth recognising early so you stop trying. If the pack is built for a line above yours, it will not load — there is no setting for it.
If you are deliberately staying on an older version — plenty of people are, for a server or a world they would rather not migrate — the workable answer is not to fight the newest releases but to filter the catalogue to builds made for your line. Older versions are far better served than people expect: packs targeting 1.16 and 1.17 are still a large share of everything published, because they were finished, they worked, and their authors moved on.
What is not the problem
Three theories we see constantly in support messages, all of which send people down the wrong path:
- "The file is corrupted." Almost never. A genuinely broken archive fails at import with a visible error. A pack that imports cleanly and then does nothing is a version or scripting problem, not a damaged file.
- "I need to reinstall Minecraft." It does not help, and you risk your worlds. Nothing in the failure mode above lives in the game installation.
- "The addon was removed / patched by Mojang." Mojang does not disable third-party addons. What happens is that the interface the addon relied on moved.
Still nothing?
Work through the general checklist in Addon not showing up or won't import — it covers activation, wrong edition and app-version problems, which account for most of what is left after the version issues above.
If the addon consists of two halves — a behaviour pack and a resource pack — and only one imported, that is its own failure mode and it is worth checking separately: half an addon activates perfectly and does half of nothing.