This guide takes you through the steps required to create a dedicated SCP:SL server on Windows and Linux.
Minimum Server Specifications
- 4 GB RAM
- 2 core CPU
- ~600 MB storage space
Windows Instructions
Prerequisites
- SteamCMD - Used to install and update the server
- Mono (64-bit) - Framework used by Unity for a lot of things, needed to fix certain voice chat issues
- Visual C++ Redistributable 2015
Installing the SCP:SL dedicated server with SteamCMD
SteamCMD is used to install the SCP:SL server in a specified location, this will also make it easier to update the server once one is required.
Logging in
To be able to download the server you must be logged into steam.
You can also log in with a steam account but that isn't recommended nor needed.
login anonymous
Setting install directory
To set the desired server directory/install location.
force_install_dir <directory> - (eg. C:/SL_Server)
Installing it
To install the dedicated server the app ID 996560 is used, it is the headless build of SCP:SL and will run more efficiently than if the game itself was used to host.
app_update 996560
Validating
To make sure that none of the required files are missing or corrupted.
app_update 996560 validate
(Optional) Creating an update script
A batch file can be created to have the server automatically updated when needed.
Paste the following code into a batch file and run it once the server needs an update.
steamcmd
+login anonymous
+force_install_dir <directory>
+app_update 996560
+app_update 996560 validate
+quit
Linux Instructions (Ubuntu/Debian)
Prerequisites
- An already set-up server with SSH and FTP configured
Installing components
Mono - Framework used by Unity for a lot of things, needed to fix certain voice chat issues
tmux - Allows running multiple windows in a single session, in our case it used to keep the server running without having to be logged into it
sudo apt-get install tmux
SteamCMD - Used to install and update the server
sudo apt-get install steamcmd
Creating new user
A new user will be created to be specifically used for the SL server, as using the root user is insecure.
sudo adduser scpserver - Creates a new user with the name "scpserver"
su - scpserver - Changes active user to "scpserver"
Installing the SCP:SL dedicated server with SteamCMD
SteamCMD is used to install the SCP:SL server in a specified location, this will also make it easier to update it once one is required.
Opening SteamCMD To be able to execute the commands required for the install. Must be ran in the directory the steamcmd.sh is installed in.
./steamcmd.sh
Logging in
To be able to download the server you must be logged into steam.
You can also log in with a steam account but that isn't recommended nor needed.
login anonymous
Setting install directory
To set the desired server directory/install location.
force_install_dir <directory> - (eg. /home/SL_Server)
Installing it
To install the dedicated server the app ID 996560 is used, it is the headless build of SCP:SL and will run more efficiently than if the game itself was used to host.
app_update 996560
Validating
To make sure that none of the required files are missing or corrupted.
app_update 996560 validate
Starting up the server
On linux starting the server is a bit different than on windows.
tmux new -s scp - Starts new session with name "scp"
cd <directory> - Select server directory
./LocalAdmin 7777 - Starts up the server with LocalAdmin on the port 7777
Server Configuration
Main article: Server Config
After installing the server can be configured, and settings such as the server name, info tab, player count and similar can be set.
All of these settings can be changed in the config_gameplay.txt/config.txt file.
- On Windows: %AppData%\Roaming\SCP Secret Laboratory\config\<port>\config_gameplay.txt
- On Linux: ~/.config/SCP Secret Laboratory/config/<port>/config_gameplay.txt
Verification
The server must be verified to be visible in the Server Browser.
Before requesting verification make sure your server follows the Verified Server Rules.
Requesting Verification
Once ready send an email to [email protected] with the following info:
- The server's external IPv4 address
- The port used by the server
- If the server IP is static or dynamic
Once sent make sure to keep your server running until it is verified, the verification process usually takes less than 72 hours.
