Forge Server Tools · every failure mode · guides

Missing or unsupported mandatory dependencies Minecraft server

A mod is missing a dependency — FATAL

What this actually means

One of your mods declares a hard dependency that is absent, or present at the wrong version. Forge refuses to start rather than load a mod whose requirements aren't met.

How to fix it

Install the named dependency at the version range the log asks for. Watch the version range syntax: [1.2,) means 1.2 or newer, [1.2,2.0) means 1.2 up to but NOT including 2.0. A dependency that is 'installed' but one major version off counts as missing.

How to be sure it is this

The log states the dependency and the version range it wants. If what you have is inside that range, the dependency is not the problem.

What it gets mistaken for

A library that is too NEW fails identically to one that is missing. [4.2.0,4.3.0) excludes 4.3.0, so installing the newest release can cause the very error you are trying to fix.

What to do next

Install exactly what the range asks for. If two mods demand incompatible versions of the same library, one of them has to go — there is no configuration that resolves it.

What it looks like in your log

Search your crash report or latest.log for any of these:

requires
Missing or unsupported mandatory dependencies
requires
MissingModsException

The free edition of Forge Server Doctor detects this one. It is a single Python file with no dependencies — point it at the report and it names the cause and the mod jar:

python3 forge_doctor_free.py crash-reports/crash-....txt