A mod is missing a dependency
Applies to Forge, NeoForge.
What it looks like in your log
Mod ID: 'geckolib', Requested by: 'alexsmobs', Expected range: '[4.4.2,)', Actual version: '[MISSING]'
What causes it
The loader stopped because a mod declares a dependency that is not satisfied.
How to fix it
The loader lists every unmet dependency in one block: install each named mod for this exact Minecraft and loader version, or remove the mod that asks for it.
Why it happens
Forge and NeoForge print one block per unmet dependency: the mod id that is missing, the mod that requested it, the version range it wanted and the version actually present, where [MISSING] means not installed at all. It is the most complete error the loader produces, and it is read wrongly more than any other, because people look at the first line and stop.
Fix it step by step
- 1Read every blockThe loader reports all unmet dependencies together. Note each "Mod ID" and each "Requested by".
- 2Install the missing onesFind each mod id on CurseForge or Modrinth, download the build for your exact Minecraft version and loader, and put it in mods/. The requesting mod's page usually links it under Relations.
- 3Fix the version rangesIf "Actual version" is present but outside "Expected range", update the dependency to a version inside the range. [4.4.2,) means 4.4.2 or newer.
- 4Restart once, after all of themRestarting after each one turns a five-minute job into an hour.
If that didn't work
If a dependency is present, in range, and still reported missing, check for a Forge mod in a NeoForge pack or the reverse. The two loaders do not read each other's jars.
Not sure this is your problem? Paste your log and Roastd will tell you which of these it actually matched, and what else it found.
Check your own log