Your mod isn't broken. It's built for another Minecraft version.
A mod that installs cleanly and then does nothing is the most demoralising kind of failure, because there is nothing to fix — no error, no missing file, no obvious step you skipped. In a large share of these cases the file is perfectly healthy. It was simply built for a different version of Minecraft than the one you are running, and neither the game nor the download page bothered to say so. I pulled the numbers across our whole catalogue to show how common that actually is.
Most content targets exactly one version
This is the root of it. Of the Bedrock add-ons that declare which versions they are for, 13,277 name exactly one — 43% of them. On Java it is worse: 132,443 mods name a single version, just over half of everything that declares at all.
| Versions declared | Bedrock | Java |
|---|---|---|
| Exactly one | 13,277 | 132,443 |
| Two or three | 6,132 | 47,013 |
| Four or more | 11,389 | 80,436 |
A single-version mod is not a badly made mod. It is usually a mod whose author rebuilds it for each Minecraft release and uploads each build separately. That is the correct thing to do — and it is exactly what makes shared links go stale. Someone posts a link in a chat in March, you tap it in August, and you receive a file built for the game as it was five updates ago.
The tell: if a mod installs, activates, and produces absolutely nothing — no new items, no new mobs, no visible change — check the version before you check anything else. A genuinely corrupt file usually fails earlier and louder.
What the Bedrock catalogue actually covers
| Version | Add-ons |
|---|---|
| 1.21 | 8,147 |
| 26.10 | 6,056 |
| 26.30 | 5,475 |
| 26.0 | 5,355 |
| 26.20 | 5,166 |
| 1.21.130 | 4,811 |
| 1.19 | 4,589 |
| 1.20 | 4,569 |
If the numbers beginning with 26 look like corrupted data, they are not. Bedrock moved to a year-based naming scheme, so 26.x is the 2026 line and it sits above 1.21, not below it. We had to teach our own filters that, and plenty of tools out there still sort those releases to the bottom as though they were ancient. If your game reports a 26.x version, look for content on the 26.x lines rather than assuming everything modern is labelled 1.21.
Two different claims, and only one of them is measured
There are two separate statements about version on any add-on page, and they come from completely different places.
- "Works with 1.21" — what the author wrote on the upload page. It is a claim, it is often copied forward from the previous release, and nobody verifies it.
- "Manifest requires 1.21.0 or newer" — read by us out of the pack file itself. Minecraft reads the same line and refuses to load a pack whose floor is above your game.
We keep those apart deliberately. On our mod pages the second one appears under "Verified by MCModsHub" — because it is a measurement of the file we are actually handing you, not a repetition of someone's description. Where the two disagree, the manifest wins, every time.
The floor is a minimum and not a ceiling. A pack asking for 1.16.0 will usually still load on a 2026 build. The reverse never works: a pack asking for 1.21.0 will not load on 1.20, and the message Minecraft shows for that is vague enough that most people conclude the download is corrupt.
Java: the loader gap nobody warns you about
On Java there is a second version to match — not just the game, but the mod loader. And here the catalogue shows something worth knowing before you commit to a setup. These are the mods available for the 1.21 line, by loader:
| Loader | Mods for 1.21.x |
|---|---|
| Fabric | 25,123 |
| NeoForge | 19,084 |
| Spigot / server plugins | 10,916 |
| Forge | 5,378 |
| Quilt | 2,237 |
Look at the bottom two rows. Forge has 5,378 mods for 1.21.x against Fabric's 25,123 — 4.7 times fewer. That gap is not visible anywhere on a download page; you only see it after you have installed Forge and started hunting for mods that fail to exist. If you are setting up a fresh 1.21 profile and have no strong reason to pick Forge, Fabric or NeoForge will give you a far wider catalogue.
Across all versions the ranking looks different — Forge has 34,692 mods in total, and Spigot leads outright with 79,527 — because Forge's library is deep in older versions where it dominated for years. Which is another way of saying the same thing: on Java, "how many mods exist" is meaningless without naming a version and a loader.
1.20.1 refuses to die, and that's fine
The single most supported Java version in the catalogue is not the newest one. It is 1.20.1, with 80,385 mods, ahead of 1.21.1 at 61,927. 1.8 still carries 35,174, kept alive almost entirely by PvP servers.
Big modpacks pin a version and stay there for years, and mod authors follow the players rather than the release notes. So if you are chasing a specific mod that only exists for 1.20.1, running an older profile is a completely reasonable choice — not a compromise. Minecraft launchers let you keep several profiles side by side precisely for this.
How to check in ten seconds
- Know your version. Bedrock shows it in the bottom corner of the main menu. Java shows it in the launcher next to the profile.
- Read the manifest line, not the description. On our pages, "Manifest requires Minecraft X or newer" is the measured one. If your game is below X, stop there — nothing else will help.
- On Java, match three things: game version, loader, and loader version. A Fabric mod for 1.21.1 will not load on Fabric for 1.20.1.
- If the link came from a chat or a video, assume it is stale. Search the mod by name and take the current build instead.
We filter the catalogue by version for exactly this reason — you can browse Bedrock add-ons or Java mods narrowed to the version you actually run, so the stale builds never reach you in the first place. And if something still misbehaves, the guides cover the rest: an add-on that doesn't show up, and a Java mod that won't load.