We read 24,197 "this mod is broken" reports. Only 17% were about the mod.
Every report sent from our app asks one extra question: where did it go wrong? Not "is it broken" — where. Between 16 June and 2 August we collected 24,197 of them across 6,518 different mods, and the answer reshaped how we think about the whole catalogue. The add-on itself misbehaving — imported fine, then wrong in the game — accounts for 16.7%. Everything else failed earlier, in places most people never think to look.
Where the failures actually land
Four stages, because there are four places a pack can die between a listing and a working world.
| Where it failed | Reports | Share |
|---|---|---|
| Download - the file never arrived | 8,629 | 35.7% |
| Import - Minecraft would not open it | 8,477 | 35.0% |
| In game - imported, then wrong | 4,045 | 16.7% |
| Something else | 3,045 | 12.6% |
70.7% of the pain happens before the add-on gets a chance to be good or bad. That is the single most useful thing we have learned from running this catalogue, and it is not what we expected. The instinct is to blame the pack. The data says the pack usually never got to play.
Stage one: the file never arrived
A third of all reports. Most mods are not hosted by us - they live on the site the author published them to, and we send you there. Which means the download depends on somebody else's server being up, on their CDN answering in your country, and on the link still pointing at a file that exists.
Links rot quietly. An author replaces a file, renames a project, or their host moves things around, and nothing anywhere announces it. The listing stays up and looks perfectly healthy while the download behind it returns nothing.
What we do about it: every download link in the catalogue gets re-checked on a schedule, and the most-opened mods get re-checked every hour, so a top mod that broke this morning is caught the same day rather than next week. When a file is genuinely gone, we hide the entry instead of leaving a dead link to be discovered one disappointed download at a time. Where an author allows it, we host a copy ourselves so the download stops depending on anyone else.
What you can do: if a download stalls at zero, try once more on a different network before giving up. A meaningful share of these are regional - the file is alive and simply unreachable from where you are. If it still fails, report it; that report is what triggers the re-check.
Stage two: Minecraft would not open it
Another third, and this one is almost entirely fixable. The file arrived. You tapped it. Minecraft either did nothing at all, or opened and announced that it could not identify the pack.
The usual cause is boring and infuriating: the extension is wrong. Minecraft Bedrock decides what to do with a file almost entirely by its ending. A .mcpack is a single pack. A .mcaddon is a bundle of several. A .mcworld is a world. Underneath they are all zip archives with different insides, and if a file is named .mcpack while actually containing two packs in subfolders, Minecraft opens it, finds a structure it did not expect, and gives up.
Authors mislabel constantly, because on a desktop it often still works and nobody notices. On a phone it does not.
What we do about it: rather than trusting the name a source gave us, we read each archive's own structure and serve the extension that matches what is really inside. It is one of the cheapest fixes in the whole system and one of the highest-yield.
What you can do: open the file from our app's Downloads tab rather than from a file manager. The file manager hands Minecraft whatever name the file happens to carry; we hand it the corrected one. And if Minecraft is not installed or badly out of date, nothing will open at all - which sounds obvious until it happens to you.
Stage three: it imported, and then it was wrong
4,045 reports - the ones people mean when they say a mod is broken. These split into a handful of causes that repeat endlessly:
- Half a pack. The add-on needs a second pack it does not include, so you get mobs with no textures or textures with no mobs. Around 7.6% of the add-ons we have opened are in this state. Details in what actually installs.
- Experiments switched off. 1,560 packs do nothing until you enable Beta APIs in that specific world, and they draw 3.5 times the complaint rate of everything else. Full write-up: the toggle nobody mentions.
- Built for a different Minecraft. A pack declares a minimum version, and an older game ignores the parts it cannot read - silently. See your mod isn't broken, it's for another version.
- Genuinely broken by the author. A malformed manifest, entities in a behaviour pack with nothing to draw them, dependencies on beta modules the game removed years ago. This is the smallest group and the only one where the honest answer is that the pack cannot be saved.
Why the split matters: "this mod is broken" is four completely different problems wearing the same sentence, and three of them have nothing to do with the mod. Sorting them is what lets an answer be specific instead of a shrug - and it is why a report to us gets a reply about your actual failure rather than a generic reinstall suggestion.
What we changed because of this
Knowing where failures land changed what we build. We stopped treating a report as a complaint to be filed and started treating it as a measurement. Every report now runs through the same check we would run by hand: is the link alive, is the extension right, does the archive contain what it claims, does the manifest ask for something your game does not have. The answer goes back to the person who reported it, usually within the hour, and it names the actual cause.
It also changed what we hide. A mod whose file cannot be delivered is worse than no mod at all - it costs somebody a download, a wait, and a disappointment. Those come out of the listings until they are fixed, and they go back in the moment they are.
The short version
- Nothing downloaded? Try a different network, then report it. It is probably not your phone.
- Downloaded but Minecraft ignored it? Open it from the Downloads tab in our app, not the file manager.
- Imported but nothing changed? Activate both packs, then check Experiments in that world.
- Mobs with no textures? You have half a pack - find the other half or a different upload.
Longer versions live in our guides, including installing Bedrock add-ons and what to do when an add-on does not show up.