1,560 add-ons need one Minecraft toggle. Here is which ones, and why nobody tells you.
There is a switch buried three menus deep in Minecraft Bedrock that decides whether a whole class of add-ons works or sits there doing nothing. It is off by default. Almost no download page mentions it. We opened 32,897 Bedrock packs to see which ones need it, and the answer is 1,560 — about one in twenty-one. Those 1,560 draw three and a half times more "it's broken" reports than every other pack in the catalogue, and in most cases nothing is broken at all.
What the switch actually is
Minecraft Bedrock ships some of its scripting and gameplay capability as opt-in. In your world settings it appears under Experiments, with names like Beta APIs, Holiday Creator Features or Molang Features. An add-on that uses those capabilities declares it in its manifest — the small file Minecraft reads when it decides what a pack is allowed to do.
If the pack asks for a capability your world has not enabled, Minecraft does not warn you. It does not refuse the import, it does not grey the pack out, and it does not put a message anywhere you will see it. The pack imports, appears in your list, activates — and then its content simply is not there.
That silence is the whole problem. From the player's side an add-on that needs Experiments and an add-on that is genuinely broken look exactly the same.
How many packs are affected
Because we download and unpack every Bedrock file we can reach, we read those manifests ourselves rather than trusting a description. Of the packs opened so far:
| Manifest asks for | Packs | Share |
|---|---|---|
| Nothing experimental — works as shipped | 31,337 | 95.3% |
| Experimental capability — needs the toggle | 1,560 | 4.7% |
One in twenty-one sounds small until you notice which packs they are. Experiments are what a pack needs to add real behaviour — custom mobs that do something, scripted events, new mechanics. The packs that need the toggle are disproportionately the ambitious ones, which is exactly why people are disappointed when they appear to do nothing.
What it costs, in complaints
This is the part we could only answer because both halves of the data sit on our side: what is inside the pack, and how often people who opened that pack told us it was broken.
Over the week of 27 July to 2 August, packs that need Experiments were opened 216,530 times and drew 465 reports. Everything else was opened 2,030,974 times and drew 1,258. Per thousand opens:
| Pack type | Opens | Reports | Per 1,000 |
|---|---|---|---|
| Needs Experiments | 216,530 | 465 | 2.15 |
| Everything else | 2,030,974 | 1,258 | 0.62 |
3.5 times the complaint rate — and we normalised by opens rather than counting per pack, precisely so that "these are just the popular ones" cannot explain it away. A gap that size, on a difference that is one checkbox, is not a content quality problem. It is an instruction problem.
The honest caveat: a report means somebody told us a mod did not work. We cannot prove every one of those 465 was caused by a missing toggle. What we can say is that the only systematic difference between the two groups is the manifest requirement, and the gap does not shrink when you account for how often each group is opened.
How to turn it on
The toggle lives per world, not per device. This trips up more people than the setting itself.
- From the Minecraft main menu choose Play, then find your world and tap the pencil next to it to edit its settings. For a brand new world, the same section appears while you are creating it.
- Scroll the left-hand list to Experiments.
- Switch on Beta APIs. If the add-on's page mentions Holiday Creator Features or Molang Features, switch those on too.
- Confirm the warning, then activate the add-on's packs in Resource Packs and Behaviour Packs as usual, and load the world.
Two things worth knowing before you do it. Enabling Experiments disables achievements in that world permanently — it cannot be undone for that world, so use a copy if the achievements matter to you. And because the setting is per world, turning it on in one world does nothing for the others; an add-on that worked yesterday and does nothing today usually means you are in a different world, not that the pack broke.
The ones the toggle will not save
A smaller group is genuinely beyond rescue: 134 packs in our catalogue ask for experimental modules so old that current Minecraft no longer offers them. The author built against a beta that has since been folded into the game under a different name, or removed outright. No amount of switching things on brings those back — the pack needs its author to update it.
We flag those separately rather than pretending the toggle will help, and we hide the worst of them from listings entirely, because sending somebody off to enable Experiments for a pack that cannot work either way is a worse outcome than not showing the pack at all.
Spotting it before you download
On our mod pages the "Verified by MCModsHub" panel is built from the file we actually opened, not from the description the uploader wrote. When a manifest asks for experimental capability, the panel says so, and our app shows the same chip on the mod card before you commit to a download.
It is the same principle as everything else we publish: the uploader tells you what the pack is supposed to do, and we tell you what is inside the file. When those two disagree, the file wins.
If it still does nothing
Experiments is the first thing to check, not the only thing. Working through it in order:
- Both packs activated? Most add-ons ship a behaviour pack and a resource pack. One without the other gives you invisible mobs or decorations that do nothing.
- Experiments on, in this world? Per world, every time.
- Is your Minecraft new enough? Packs declare a minimum version, and an older game silently ignores what it cannot read. We cover that in why a mod says it was built for another Minecraft version.
- Did you get the whole pack? Around 7.6% of the add-ons we opened depend on a pack they do not include - the single most confusing failure in Bedrock, and the subject of what actually installs.
Step-by-step versions of all of it live in our guides, including installing Bedrock add-ons and what to do when an add-on does not show up.