> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wasabihosting.com/llms.txt
> Use this file to discover all available pages before exploring further.
# How to Install Mods on a Squad Server
> Install Steam Workshop mods on your Squad server hosting - custom maps, factions, and overhauls, with layer rotation setup and version syncing tips.
Squad mods are distributed through the **Steam Workshop** — custom maps, new factions, weapon packs, and full gameplay overhauls. The server downloads and loads the mods, you add their layers to your rotation, and **players auto-download the mods when they join**. This guide covers the workflow on managed hosting and the version-syncing gotchas every modded server hits eventually.
## How Squad Mods Work
1. Every Workshop mod has a numeric **Workshop ID**, found in its Steam Workshop page URL (the `id=` parameter).
2. The server needs the mod's files downloaded and placed into its mods folder. Under the hood this is a SteamCMD `workshop_download_item` download of the Workshop item for Squad.
3. Once loaded, the mod's **layers** become available — but they only get played if you add them to your rotation.
4. Clients joining your server automatically download the same Workshop items through Steam before connecting.
## Installing Mods on Wasabi Hosting
Browse the Steam Workshop for Squad and note the **Workshop ID** of each mod you want (from the page URL). Check recent comments/ratings first — abandoned mods break after game patches.
Depending on your service setup, install mods via the [Game Panel](https://panel.wasabihosting.com) (mod/Workshop options or the **Startup** tab where available), upload the mod files through the File Manager or SFTP, or simply [open a ticket](https://billing.wasabihosting.com/submitticket.php) with the Workshop IDs and we'll set them up for you.
Installed is not the same as played. Get the layer names from the mod's Workshop page (authors list them) and add them to your rotation file, one per line — see [Server Configuration](/games/squad/server-configuration):
```ini theme={null}
SomeModMap_RAAS_v1
SomeModMap_Invasion_v1
Yehorivka_RAAS_v1
```
Restart the server from the panel, watch the console for the mod loading successfully, then join in-game — your client will download the mod and you can `AdminChangeLayer` to a modded layer to confirm (see [Admin Setup](/games/squad/admin-setup)).
## Clients Auto-Download on Join
Players don't install anything manually — joining your modded server triggers the Workshop download on their side. Two things to communicate to your community:
* **First joins are slow.** Large mods run into multiple gigabytes; tell players to expect a wait the first time.
* **Mods persist client-side**, so subsequent joins are quick until the mod updates.
## Version Syncing After Mod Updates
This is the number-one operational issue on modded Squad servers: **the server and every client must run the same version of each mod.**
* When a mod author publishes an update, clients get the new version from Steam automatically — but your **server keeps the old files until it re-downloads the mod**. Result: players suddenly can't join.
* After any mod update, update the mod on the server (re-run the install/update via the panel, or ask support) and **restart**.
* After a **Squad game patch**, expect some mods to be broken until authors update them. If the server crashes or players can't join post-patch, temporarily pull the suspect mod from the server and its layers from the rotation.
Schedule mod updates for quiet hours and announce them with `AdminBroadcast` before restarting — your regulars will thank you.
## Popular Mod Types
| Type | Examples of what they add |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Maps** | New terrains with their own RAAS/AAS/Invasion layers — the easiest mods to slot into an existing rotation |
| **Factions** | New armies, weapons, and vehicles usable on supported layers |
| **Gameplay overhauls** | Full-conversion experiences (hardcore realism rulesets, era conversions like WWII or Vietnam-style mods) — these usually replace your whole rotation |
| **Admin/utility** | Server-side tweaks and quality-of-life tools |
## Watch Your Disk and Downloads
Big mods cost twice: **long downloads** for every new player joining, and **disk space** on the server — a handful of large conversion mods can consume tens of gigabytes. Keep the mod list lean, remove mods you no longer rotate, and check your storage usage in the panel. NVMe storage on Wasabi Hosting keeps mod loading fast, but space is still finite.
## Troubleshooting
The layer names in your rotation probably don't match the mod's actual layer names — check the exact spelling on the mod's Workshop page and fix the rotation file. Invalid layers are skipped silently, so a typo just means the rotation moves on without them.
Classic version desync: the mod updated on Steam (clients got the new version) but the server still has the old files. Update the mod server-side and restart. Check the mod's Workshop changelog to confirm a recent update.
Usually a mod broken by a recent Squad patch. Remove the mod's layers from the rotation (and the mod itself if the crash happens at startup), restart, and watch the mod's Workshop page for a compatibility update before re-adding it.
## Related Guides
Rotation files and layer naming for your modded layers.
What the mod download looks like from the player side.
Planning a heavily modded server? [Get a Squad server](https://wasabihosting.com/game-servers/squad) from €16.00/month — NVMe storage and easy upgrades when your mod folder grows.