Citadel and Content Mods: Understanding Dependencies

Players choose content mods for their worlds, creatures, and activities. A shared library fits beneath that choice. Keeping those two roles separate helps you understand which project is responsible for a feature or an error.

Start with the experience you want

Read the content mod description and decide whether it suits your preferred style of play. Consider exploration, building, progression, and the amount of change you want in a world. The dependency list then tells you which supporting projects must accompany that choice.

Follow the dependency chain

Check requirements on the exact release you download. A project relationship can change between versions, so a guide written for another release is not enough. Install each required dependency in the same instance and use the loader requested by that content release. Optional integrations should be considered separately from requirements that prevent the game from loading.

Attribute features and problems correctly

If you see a creature, structure, or gameplay system, identify the content mod that adds it before changing configuration. If the loader rejects a missing library, resolve that dependency first. This distinction keeps troubleshooting focused and gives a maintainer a clearer report than describing every issue as a Citadel problem.

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: Planning an Exploration Modpack Around Shared Libraries