SCP:SL has a lot of server settings. Most guides dump the entire config reference on you and call it a day. That’s not very helpful when you just want to know which settings actually change how your server feels to play on.
This guide groups the settings that matter by server type, so you can find the ones relevant to what you’re building without reading through every option.
Where to Find Your Config Files
SCP:SL stores its configuration in two main files:
- config_gameplay.txt - all game rules (player limits, friendly fire, spawn timers, round settings)
- config_remoteadmin.txt - admin permissions, roles, and moderation settings
File location on Linux:
~/.config/SCP Secret Laboratory/config/<port>/Replace <port> with your server’s port number (default 7777).
On managed hosting, these files are accessible through your host’s file manager or SFTP. On WinterNode, navigate to /.config/SCP Secret Laboratory/config/<port>/ in the File Manager panel.
Always Restart After Editing
Config changes don’t apply until you restart the server. SCP:SL doesn’t hot-reload settings.
Settings Everyone Changes First
These are the settings you’ll probably want to adjust before your first real session, regardless of what kind of server you’re running.
| Setting | File | Default | Notes |
|---|---|---|---|
server_name | config_gameplay.txt | (empty) | What players see in the server browser |
max_players | config_gameplay.txt | 20 | No hard cap - raise it if your hardware supports it |
server_password | config_gameplay.txt | (empty) | Leave empty for public servers |
friendly_fire | config_gameplay.txt | false | Biggest single gameplay change you can make |
contact_email | config_gameplay.txt | (empty) | Required for server verification |
Your server name is what sets first impressions in the browser. Keep it readable and descriptive. Avoid excessive special characters or misleading tags - Northwood’s Verified Server Rules restrict what you can put in the name.
Settings by Server Type
Rather than listing every option alphabetically, here are the settings that matter for each common server style.
Casual/Friends Server
Playing with a small group who just want to have fun without heavy moderation.
| Setting | Recommended Value | Why |
|---|---|---|
friendly_fire | false | Prevents frustration in casual groups |
max_players | 15-25 | Sweet spot for casual rounds |
auto_round_restart_time | 15-20 | Give everyone a breather between rounds |
minimum_MTF_time_to_spawn | 240 | Slightly faster respawns keep the action going |
maximum_MTF_time_to_spawn | 300 | Shorter max wait for respawn waves |
The default settings are actually fairly close to ideal for casual play. The main thing is keeping friendly fire off - nothing kills the fun faster than teammates shooting each other by accident (or “by accident”).
Competitive/Serious Server
Focused gameplay where skill and teamwork matter. Usually attracts experienced players.
| Setting | Recommended Value | Why |
|---|---|---|
friendly_fire | true | Core mechanic for competitive play |
friendly_fire_multiplier | 0.4-0.6 | Punishes careless shooting without instant kills |
max_players | 25-35 | Enough for dynamic rounds without chaos |
minimum_MTF_time_to_spawn | 280 | Default timing works well for pacing |
maximum_MTF_time_to_spawn | 350 | Standard respawn window |
ci_respawn_percent | 35 | Default is balanced. Raise to 40-45 if CI feels underrepresented |
The friendly fire multiplier is key here. Setting it to 1.0 (full damage) makes the game punishing. Something in the 0.4-0.6 range means careless shooting has consequences without making every accidental hit lethal.
Roleplay/Custom Server
Servers focused on roleplay, custom rules, or unique gameplay modes. Usually heavily moderated with EXILED plugins.
| Setting | Recommended Value | Why |
|---|---|---|
friendly_fire | true | Roleplay requires consequences |
intercom_max_speech_time | 30-45 | More time for RP announcements |
intercom_cooldown | 60-90 | Shorter cooldown for more communication |
auto_round_restart_time | 25-30 | Longer breaks for RP setup between rounds |
warhead_tminus_start_duration | 120-150 | More time for RP during warhead events |
Roleplay servers live and die on communication tools. Extending the intercom speech time and reducing the cooldown gives players more opportunity for in-character announcements. Most RP servers also run plugins like EXILED for custom roles and rules enforcement.
Spawn and Round Settings
These control the pacing of each round - how long rounds last, how often reinforcements arrive, and the balance between factions.
| Setting | Default | What It Controls |
|---|---|---|
minimum_MTF_time_to_spawn | 280 seconds | Earliest MTF/CI respawn wave |
maximum_MTF_time_to_spawn | 350 seconds | Latest MTF/CI respawn wave |
ci_respawn_percent | 35% | Chance that a respawn wave is Chaos Insurgency instead of MTF |
warhead_tminus_start_duration | 90 seconds | Countdown timer for the Alpha Warhead |
auto_round_restart_time | 10 seconds | Delay after round end before the next one starts |
The MTF spawn timing is one of the most impactful settings for round pacing. Shorter timers mean dead players get back into the action faster, but it also means SCPs face more resistance sooner. Longer timers give SCPs more time to establish dominance before reinforcements arrive.
The CI respawn percentage affects faction balance. At 35% (default), roughly one in three respawn waves is Chaos Insurgency. Raising this shifts the balance toward D-Class escape scenarios and away from Foundation containment.
Intercom Settings
The intercom is one of SCP:SL’s most unique features - it broadcasts audio to the entire server. These settings control how it works.
| Setting | Default | Notes |
|---|---|---|
intercom_max_speech_time | 20 seconds | How long someone can talk per use |
intercom_cooldown | 120 seconds | Wait time between uses |
The defaults are conservative. For servers where communication matters (RP, organized competitive), consider extending speech time to 30+ seconds and reducing cooldown to 60-90 seconds.
Remote Admin Setup
Remote Admin is your in-game moderation tool. Press M to open it once you have permissions configured.
Adding Yourself as Owner
In config_remoteadmin.txt, find the Members: section:
Members:
- YourSteamId64@steam: owner
- FriendsSteamId64@steam: admin
- ModeratorSteamId64@steam: moderatorGet Steam64 IDs from a SteamID lookup tool or from the server console when players join.
Default Role Permissions
| Role | Can Do | Can’t Do |
|---|---|---|
| Owner | Everything | Nothing restricted |
| Admin | Kick, ban, round management, player teleport | Server shutdown, config changes |
| Moderator | Kick, mute, basic player management | Bans, round manipulation |
You can create custom roles with granular permissions in the same file. The format is documented within config_remoteadmin.txt itself.
Syntax Is Sensitive
config_remoteadmin.txt is notoriously picky about formatting. A missing space, wrong indentation, or stray character can break permissions without any error message. If your admin commands stop working after an edit, carefully compare your changes against the example format in the file.
Common Mistakes
Editing the wrong port’s config. If your server runs on port 7778 but you edited the config in the 7777 folder, nothing changes. Check your actual port number.
Forgetting to restart. Config changes require a server restart. No exceptions, no hot-reload.
Breaking config_remoteadmin.txt syntax. This file is sensitive. If something stops working after an edit, revert and try again with careful attention to the format.
Setting max_players too high for your RAM. SCP:SL uses more memory per player than most games because every player is a fully simulated entity with inventory, roles, and status effects. If you set max_players to 40 on a 3GB server, you’ll crash. See our RAM guide for recommendations.
Ignoring Verified Server Rules. If your server is verified, certain settings and behaviors are required by Northwood’s rules. Violating them can get your verification revoked, which removes you from the server browser.
What Settings Don’t Fix
Some common server issues look like config problems but aren’t:
- Player lag or desync - usually a network or hardware issue, not a settings issue. Check your server’s location relative to your players and your RAM allocation.
- “The server feels empty” - that’s a community-building problem, not a config problem. Get verified, promote your server, be consistent about uptime.
- Plugin conflicts - if something weird started happening after adding a plugin, the plugin’s config is the place to look, not the base game config. See our plugin guide.
Frequently Asked Questions
Set friendly_fire to true in config_gameplay.txt and restart the server. You can also adjust the damage multiplier with the friendly_fire_multiplier setting if you want reduced (but not zero) team damage.
Yes. SCP spawn chances and class distribution are configurable in config_gameplay.txt. You can adjust how often specific SCPs appear and the overall SCP-to-human ratio.
Edit config_remoteadmin.txt and add entries under the Members section using the format 'SteamId64@steam: rolename'. Default roles are owner, admin, and moderator. Restart the server for changes to take effect.
On Linux: ~/.config/SCP Secret Laboratory/config/<port>/. The two main files are config_gameplay.txt (game rules) and config_remoteadmin.txt (permissions). On managed hosting, access them through your host's file manager.





SCP: Secret Laboratory