A Citadel Setup Checklist for Modded Servers
A server adds a second installation to maintain. Dependency requirements must be checked for the server environment as well as each player instance, with the exact expectations determined by the mods you run.
Read the server requirements
Confirm that each content mod supports a dedicated server and list its required dependencies. Review the file details for your Minecraft version and loader. Keep client-only utilities separate from server requirements, and follow project documentation rather than copying every file indiscriminately.
Keep a shared release manifest
Maintain a simple list of the installed mod releases and loader build. Give players clear instructions for the intended client instance. When a connection fails, compare actual filenames and versions against the manifest before adjusting network or gameplay settings. A reproducible baseline is easier to support than several independently updated player folders.
Update during a planned maintenance window
Stop the server cleanly and back up the world, configuration, and current release list. Test the proposed changes with a copy of the server and a matching client. Check startup, joining, basic interactions, and saving before reopening access. Retain the previous setup so a failed update has a practical recovery path.
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.
All guides