How To Install Mods on Your Barotrauma Server
Install Steam Workshop mods on your Barotrauma dedicated server using the built-in Mod Manager or manually via LocalMods.
Barotrauma supports Steam Workshop mods that add new submarines, items, creatures, and gameplay mechanics. XGamingServer includes a built-in Mod Manager that lets you browse, install, and remove Workshop mods directly from the panel — no manual downloads needed.
The panel's Mod Manager browses the Steam Workshop and handles installation automatically.
Open the Mod Manager
In the XGamingServer Panel, click Mods in the sidebar (puzzle icon — visible on Barotrauma servers under Configuration).
Browse the Steam Workshop
On the Steam Workshop tab, search for mods by name. Sort by Trend, Total Subscribers, or Most Recent using the dropdown.
Install a mod
Click the Install button on any mod card. The button changes to "Installing..." while processing, then turns green showing Installed when complete.
Restart the server
Go to Console in the sidebar and restart the server. Mods load on startup.
Uninstall a Mod
- Switch to the Installed Mods tab
- Click the red Uninstall button on the mod card
- Confirm in the dialog
- Restart the server
The Mod Manager automatically updates config_player.xml and places mod files in LocalMods/ — you don't need to edit any files manually.
Use this method if you need to install a mod that isn't on the Workshop, or if you prefer manual control.
Download the mod on your PC
Go to the Steam Workshop for Barotrauma and subscribe to the mod. Let it fully download via Steam.
Find the mod files on your PC
The downloaded mod is at:
%LocalAppData%\Daedalic Entertainment GmbH\Barotrauma\WorkshopMods\Installed\[WorkshopID]\The [WorkshopID] is a numeric folder (e.g., 2962604067) matching the number at the end of the mod's Workshop URL.
This includes submarine mods too — custom submarines distributed as Workshop mods must be copied this way, not placed in
Submarines/.
Upload to the server
In the XGamingServer Panel, stop the server. Click Files in the sidebar, navigate to (or create) the LocalMods/ folder, and upload the entire mod folder.
Your structure should look like:
LocalMods/
ModName/
filelist.xml
[mod content files]Enable the mod in config_player.xml
In Files, open config_player.xml in the server root. Find the <regularpackages> section and add your mod:
<contentpackages>
<corepackage path="Content/ContentPackages/Vanilla.xml" />
<regularpackages>
<package path="LocalMods/ModName/filelist.xml" enabled="true" />
</regularpackages>
</contentpackages>The path must exactly match the folder name and filelist.xml location.
Load order matters. If Mod B depends on Mod A, list Mod A first.
Start the server
Start from Console and watch for mod loading errors.
Installing Multiple Mods (Manual)
Add one <package> line per mod inside <regularpackages>:
<regularpackages>
<package path="LocalMods/ModA/filelist.xml" enabled="true" />
<package path="LocalMods/ModB/filelist.xml" enabled="true" />
<package path="LocalMods/ModC/filelist.xml" enabled="true" />
</regularpackages>Do Players Need the Mods Too?
Yes — players need the same mods installed. Barotrauma tells connecting players which mods are required. If AllowFileTransfers is enabled in serversettings.xml, the server can sync some content to clients, but for Workshop mods it's generally faster for players to subscribe themselves.
Troubleshooting
| Problem | Fix |
|---|---|
| Mod not loading | Verify the path in config_player.xml exactly matches the folder name in LocalMods/. Check that filelist.xml exists at the root of the mod folder |
| "Mods/..." path errors | Older mods reference Mods/ instead of LocalMods/. Open filelist.xml inside the mod folder and update the paths |
| Mod loads but doesn't work | Check the mod's Workshop page for dependencies (e.g., Lua for Barotrauma). Install dependencies first and list them before dependent mods in config_player.xml |
| Players can't connect | All players must have the same mods installed. Mismatched mods or versions prevent connection |
config_player.xml gets reset | Stop the server before editing — the server may overwrite config files on shutdown |
| Mod already installed (panel error) | The mod is already in the Installed Mods tab. Check there first |
Related Guides
How is this guide?
