Barotrauma Mod Load Order Builder
Build your server's mod list, set the correct load order, and download a ready-to-use config_player.xml file.
Load order matters — always place dependency mods before the mods that require them.
All players must have identical mods — mismatched mod lists cause connection failures and desyncs.
Load order matters — dependency mods must appear before the mods that require them.
Stop the server before editing config_player.xml — changes made while the server is running are overwritten on shutdown.
Add a Mod
Path format: LocalMods/ModFolderName/filelist.xml for local mods, or
Mods/WorkshopModName/filelist.xml for Workshop mods.
Mod List
config_player.xml
<?xml version="1.0" encoding="utf-8"?>
<contentpackages>
<corepackage path="Content/ContentPackages/Vanilla.xml" />
<regularpackages>
<!-- Add mods using the form above -->
</regularpackages>
</contentpackages>
Place this file at %appdata%/Daedalic Entertainment GmbH/Barotrauma/config_player.xml on the server, or in the Barotrauma server data directory.
Replace the entire <contentpackages> block.
config_player.xml Structure
| Element | Purpose |
|---|---|
| <corepackage> | Always points to Vanilla.xml — the base game content. Do not remove or reorder this. |
| <regularpackages> | Contains all mod packages. Order is the load order — first entry loads first. |
| path= | Relative path to filelist.xml from the Barotrauma install folder. Case-sensitive on Linux servers. |
| enabled= | "true" or "false". Disabled mods are listed but not loaded — useful for temporarily removing a mod without deleting its entry. |
Run your own Barotrauma server.
Rent a private Barotrauma server on real hardware — full control-panel access, your mods, your configs, your rules. It's your server; run it your way.
Don't want to run it yourself? Our managed services & consulting team will set it up and keep it running for you — game servers, Windows, Linux, and cloud, from 10+ years of MSP work.