How to Troubleshoot a Missing Citadel Dependency Error

A dependency error is a useful clue. It tells you which requirement the loader could not satisfy before a world was opened. Read the complete message before replacing files.

Record what the loader requests

Copy the mod name and the required dependency range from the error. Distinguish an absent dependency from a dependency that is present but too old or otherwise incompatible. Keep the latest log from that failed launch so you can compare the result after one deliberate change.

Inspect the active mods folder

Use your launcher to open the running instance directory. Check whether Citadel is actually present, whether the file belongs to the right Minecraft version and loader, and whether duplicate releases are sitting alongside it. Files in another profile or in a nested archive will not provide the dependency expected by this launch.

Test one correction at a time

Replace the incompatible dependency with a release that meets the stated requirements and retry. If the game reports a different failure, read the new message instead of assuming the original issue remains. For unresolved cases, share the crash report and a concise version list with the relevant project support channel. Remove personal paths or other private details before posting logs publicly.

Sources and further reading

For project details, release compatibility, and developer documentation, consult the official Citadel project page, official file listing, and Citadel source repository. Checked October 17, 2026.

Read next: Citadel and Content Mods: Understanding Dependencies