To install mods on an Insurgency: Sandstorm dedicated server, authorize a separate Mod.io account for the server, subscribe that account to the required mods, enable mod loading, and then configure each mod’s mutator, map cycle, and any required Game.ini settings. Custom maps usually need a vanilla map for the initial boot so the server can download content before travelling to the modded map. Players must also sign in to Mod.io in their game client to receive the same content. This is the current post-Update 1.20 process; older instructions built around an access token in GameUserSettings.ini and a universal Mods.txt file may no longer apply.
What changed in the current post-1.20 mod workflow?
The server’s Mod.io account is now the gatekeeper for downloading community content. A dedicated-server account is authorized with a one-time security code, then used to subscribe to mods. A player account should not be reused for this purpose: current managed-host documentation warns that sharing the player account can stop downloads or create authentication conflicts.
Update 1.20 also continued the game’s mod-editor work. The release notes describe Insurgency’s origins as deeply rooted in modding and state that the editor can upload mods larger than 2 GB directly through the editor. That capability concerns uploading content; it does not configure a server, assign a mutator, or add a map to a rotation.
Many older guides show an access token in GameUserSettings.ini plus a Mods.txt list. Treat those layouts as version-sensitive legacy material. Current server panels and startup instructions generally use the separate account and security-code authorization flow described below, while the exact field names differ by provider and game build.
What do I need before installing server mods?
Gather the following before changing the server configuration:
- A working Steam dedicated server, either on your own machine or with a managed host.
- A Mod.io account created specifically for the server. Keep its email access available because authorization uses a one-time code.
- The Mod.io subscription for every mod the server must download, including dependencies named by the mod author.
- Administrative access to the host panel or to the server’s startup script and configuration files.
- The exact mutator name shown on each mod page, if that mod requires one.
- The exact custom-map name and scenario name if you are adding a map.
- A maintenance window for a restart and enough disk space for the downloaded content and its cache.
Write down the intended load order and map rotation before making changes. A subscription only makes content available to the server; it does not decide which mutator runs, which map appears in the cycle, or what gameplay settings belong in Game.ini.
How do I install mods on a managed server?
Managed panels expose the same controls that a self-hosted installation would use, but place authentication, command-line options, restarts, and logs behind web forms. The labels vary, so use the provider’s current names rather than copying an old screenshot.
1. Create a separate Mod.io account
Register an account for the server instead of using the account you play with. Use an address that the server administrator can access, because the authorization code is delivered there. Do not give the server your personal account credentials.
2. Link the account and enter the security code
Open the panel’s Mod.io, mods, or game-authentication area and start the account-linking process. Some panels place the same option in the startup configuration. Mod.io sends a one-time security code to the account’s email address; enter that code exactly as requested, then save the setting. The code is an authorization step, not a permanent replacement for the account.
If the panel reports that the code has expired, restart the linking process and use the newest message. Keep the server account logged in and authorized; repeatedly switching between accounts makes it difficult to tell whether a later failure is authentication or configuration.
3. Subscribe the server account to the required mods
Sign in to Mod.io with the server account and subscribe to every required item. Include dependency mods named by the author, not just the visible map or gameplay mod. A subscription tells Mod.io what the account is allowed to download; it does not activate the content in a match.
4. Enable mod loading and enter mutators
In the panel’s command-line or mod settings, turn on mod loading. For each mod that requires a mutator, enter the exact mutator string shown on its Mod.io page. Preserve capitalization, punctuation, and separators. The Mod.io numeric ID and the mutator name are different values: the ID identifies content for downloading, while the mutator tells the game which gameplay code to activate.
Save the command-line changes before restarting. If a mod page lists additional Game.ini values, add those in the panel’s configuration editor; downloading the package alone will not apply those settings.
5. Add custom maps to the map cycle
Add the custom map’s exact name and its scenario to the map-cycle editor. Keep a vanilla map as the first boot map when the server needs to download a custom map. A common provider pattern is:
-ModDownloadTravelTo=MAP?Scenario=SCENARIO
Replace MAP and SCENARIO with the names required by the mod page and provider. The server starts on the vanilla map, downloads the subscribed content, and then travels to the requested modded map. Starting directly on content that is not downloaded yet can leave the server stuck, return it to a vanilla map, or produce a missing-content error.
6. Restart, watch the logs, and wait for the download
Restart the server after saving account, command-line, and map-cycle settings. Watch the live log for Mod.io authentication, subscription downloads, and map travel. A first launch can take longer while files are cached. Do not repeatedly restart during an active download unless the provider’s instructions say to do so; an interrupted cache can look like an authentication failure on the next attempt.
How do I install mods on a self-hosted Steam server?
Self-hosting gives you direct access to the startup script, command line, configuration files, and logs. It also means you must perform the same account authorization and content checks without a panel that validates them for you.
- Update the dedicated-server installation and back up the startup script and configuration files.
- Create and authorize a separate Mod.io server account with the current security-code process.
- Subscribe that account to the required mods in Mod.io.
- Add the current mod-loading and authentication options to the server startup command, following the syntax for your build.
- Enter each required mutator exactly as published by the mod author.
- Place any required gameplay settings in
Game.ini, using the mod’s own instructions rather than a generic template. - Add custom maps and scenarios to the map cycle, and use a vanilla boot map with the post-download travel option when required.
- Start the server from your script, then inspect the console and log files for authorization, download, and travel results.
Older community documentation may mention files such as Start.bat, Game.ini, Admins.txt, MapCycle.txt, and Mods.txt. Those names describe historical layouts, not a guaranteed current recipe. Use them only when your installed build and the mod’s current instructions explicitly require them; do not add a legacy token or file merely because an old guide includes it.
Where do I put the Mod.io ID, and how is it different from a mutator?
Use the Mod.io ID wherever the current panel or startup syntax asks for subscribed content, then use the mutator string wherever the server enables gameplay behavior. They are separate configuration tasks.
| Value | Purpose | Where it is normally used | What happens if it is wrong |
|---|---|---|---|
| Mod.io account | Authorizes the server to access subscribed content | Account-linking panel or startup authentication | Downloads may never begin, or authentication can stall |
| Mod.io subscription and ID | Identifies the content the server should obtain | Mod subscription page, panel mod list, or current command-line field | The package is absent even though the server is otherwise online |
| Mutator name | Activates the mod’s gameplay logic | Mutator or command-line setting | Content may be downloaded but have no effect in the match |
| Map and scenario | Chooses where the server travels | Map cycle and post-download travel option | Travel fails, falls back to a vanilla map, or reports a missing map |
Game.ini settings |
Applies mod-specific gameplay options | Configuration editor or file | The mod loads with defaults or fails if required settings are missing |
Because mod authors can change names between releases, copy the current spelling from the mod’s page. Do not infer a mutator by shortening the title or by using the numeric ID.
How do custom maps download and become the first playable map?
A custom map normally downloads after the server has booted, so it is safer to start on a vanilla map and travel after the download completes. Add the custom map to the rotation, but do not assume that putting it first in the list will make it available during the initial process.
- Subscribe the server account to the map and any listed dependencies.
- Set a known vanilla map as the initial boot map.
- Configure the provider’s post-download travel option, using the exact map and scenario names.
- Restart and wait for the download messages in the log.
- Confirm that the server travels to the custom map after the content is present.
If the map never appears, check the spelling of both names and verify that the server account subscribed to the map itself. A map can be fully downloaded yet still be absent from play if the map cycle or scenario is not configured.
Do players need to subscribe to the same mods?
Players need to authenticate Mod.io in the game client. They can sign in through the in-game Mods menu and subscribe manually, or the client can download required content when they join a modded server.
Ask players to open the Mods menu and complete sign-in before troubleshooting server settings. A player who is not authenticated can experience a stalled download or a join failure even when the server account is authorized and the server has already cached the files.
Should I self-host or use a managed server?
Both approaches can run the same community content. The practical difference is who operates authentication, command-line editing, restarts, logs, and cache recovery.
| Consideration | Self-hosted Steam server | Managed hosting panel |
|---|---|---|
| Post-1.20 authentication | You create the separate Mod.io account, handle the security code, and preserve the startup configuration yourself. | The panel usually provides account-linking fields and a guided security-code workflow. |
| Command line and map cycle | Direct editing of startup scripts and map-cycle files or settings; maximum control, maximum chance of syntax mistakes. | Equivalent controls are exposed as form fields or command-line editors, with provider-specific labels. |
| Restart and logs | You schedule restarts and inspect local console or log files. | Restart buttons, live logs, and startup history are commonly built into the panel. |
| Cache recovery | You identify and clear cached mod content manually, using the current troubleshooting instructions for your build. | Some panels provide cache-clearing or reinstall controls; availability varies by provider. |
| SteamCMD and configuration work | You install, update, secure, and maintain the Steam service and every configuration file. | The provider maintains the base service while you configure the game, account, mods, and rotation. |
Choose self-hosting when you need unrestricted script and file access and are comfortable diagnosing logs. Choose managed hosting when you value guided authorization, one-click restarts, and support for cache or startup failures.
Why is my mod not downloading?
Work through authentication first, then subscription, configuration, version compatibility, and client access. Changing several variables at once hides the original cause.
- Wrong account: Confirm that the server uses a separate Mod.io account, not your player account. Reauthorize it if the panel shows an incomplete or expired link.
- No subscription: Sign in as the server account and verify that every required mod and dependency is subscribed. A player subscription does not automatically subscribe the server.
- Mod loading disabled: Check the startup command or panel toggle after every restart. A downloaded package is inert if mod loading is off.
- Mutator typo: Compare the configured mutator character by character with the current mod page. A title, display name, and numeric ID are not substitutes.
- Outdated or incompatible mod: Check whether the author marks the mod as outdated or lists additional
Game.inirequirements. An incompatible mod can prevent startup, not merely fail to appear. - Custom-map boot failure: Set a vanilla initial map and use the provider’s post-download travel pattern. Verify the map and scenario names independently.
- Client authentication: If the server is healthy but players cannot receive content, have them sign in through the in-game Mods menu before joining.
- Corrupt cache: Clear cached mod content or reauthorize only when the current provider instructions call for it. Cache locations and panel controls differ, so do not delete arbitrary folders from an old guide.
How can I change a mod safely after it is working?
Make one change at a time and keep a known-good vanilla boot map available. First record the current account status, subscriptions, mutators, map cycle, and Game.ini values. Then change the subscription or configuration, restart once, and read the log before changing anything else.
If a new mod causes startup failure, remove or disable that mod’s mutator first and restore the last working map cycle. If the server starts but the mod has no effect, check the mutator and required configuration rather than repeating the download. This separates a content problem from an activation problem.
What should the final verification checklist include?
- The server account is separate from all player accounts and remains authorized.
- Every required mod and dependency is subscribed under that server account.
- Mod loading is enabled in the current startup or panel configuration.
- Each mutator exactly matches the mod author’s current spelling.
- Required
Game.inisettings are present and valid. - The initial map is vanilla when a custom map needs post-boot downloading.
- The custom map and scenario are present in the map cycle with exact names.
- Server logs show successful authentication and completed downloads.
- Players can sign in to Mod.io in the client and obtain the required content.
Frequently Asked Questions
Why does a mod show as downloaded but not change the match?
Downloading only places the package on the server. The mod may still need its mutator enabled, a map-cycle entry, or specific Game.ini values, so inspect the mod’s current instructions for activation requirements.
Can I use one Mod.io account for both the server and my player profile?
Use separate accounts. The server’s authorization and subscriptions should remain independent from your personal profile so a player sign-in, subscription change, or security-code request cannot interrupt server downloads.
Does every mod require a mutator entry?
No. Some content is primarily a map or asset package, while gameplay mods commonly publish a mutator string. Enter a mutator only when the mod’s current page specifies one, and do not invent a name from the mod title.
Why can the server start normally while a player cannot join the modded match?
Server authentication and client authentication are separate. The player should sign in through the in-game Mods menu and allow required content to download; a healthy server process does not prove that every client has authenticated or cached the same files.
What does the 2 GB figure in Update 1.20 mean for mod installation?
The Update 1.20 notes say the editor can upload mods larger than 2 GB directly through the editor. It is an editor-upload capability, not a promise that every host, server disk, or client can immediately handle a package of any size.