Skip to content
Back to the knowledge base

Bans, whitelist and slots in SCP: Secret Laboratory

Ban and unban a player from the console in the panel, turn on the whitelist and give chosen players reserved slots on a full server.

Bans, the whitelist and reserved slots are plain text files in the .config/SCP Secret Laboratory/config/<port> folder, where <port> is the server port from the Przegląd (Overview) tab. You add a player by their account ID, such as 76561198000000000@steam. Where to get the SteamID64 shows how to find it.

The client panel is available in Polish only, so this article gives its labels in Polish with a translation the first time they appear.

Bans

Ban players from the Konsola (Console) tab in the panel or from Remote Admin in the game. Editing the bans file by hand easily goes wrong, because each entry has several fields and a time stored as a number.

Banning from the console

Remote Admin commands typed in the panel console start with a slash. The /oban command bans by account ID or by IP address, even when the player isn't on the server:

/oban 76561198000000000@steam 1d Cheating
/oban 203.0.113.10 1d Cheating

After the command, give the ban length and the reason. The length is a number with a unit, such as 30m (minutes), 12h (hours) or 7d (days). The console confirms the ban with has been banned from this server.

Bans by ID go to the UserIdBans.txt file, and bans by IP to IpBans.txt. An IP ban works only when config_gameplay.txt has ip_banning: true, which is the default.

Removing a ban

/unban id 76561198000000000@steam
/unban ip 203.0.113.10

The console answers UNBAN#Done! and the entry disappears from the file.

Whitelist

With the whitelist on, only players on the list can join the server.

  1. Add the players

    In the Pliki (Files) tab, open UserIDWhitelist.txt and enter one ID per line. Lines starting with # are ignored.

  2. Turn on the whitelist

    In config_gameplay.txt, change enable_whitelist: false to enable_whitelist: true and save the file.

  3. Restart the server

    The files are read when the server starts.
UserIDWhitelist.txt
#Put one UserID (eg. 76561198071934271@steam or 274613382353518592@discord) per line. Lines prefixed with "#" are ignored.
76561198000000000@steam
76561198000000001@steam

Add yourself and your staff too.

Reserved slots

Players on the reserved slots list can join the server even when it's full. This is useful for staff and server supporters.

Add the players to UserIDReservedSlots.txt in the same format as the whitelist, one ID per line, and restart the server. Reserved slots work when config_gameplay.txt has use_reserved_slots: true, which is the default.

Common problems

A command in the console does nothing

Remote Admin commands typed in the panel console must start with a slash: /oban, not oban. Without it, the server doesn't treat them as game commands.

A player got an automatic ban for killing their team

The server has a built-in friendly fire detector, which bans for 24 hours by default. Remove the ban with /unban id. You can change what the detector does in config_gameplay.txt, in the ff_detector_round_action and ff_detector_life_action settings, such as kick instead of ban.

Nobody can join after turning on the whitelist

Check that UserIDWhitelist.txt has IDs ending in @steam or @discord, each on a separate line, and that the server was restarted after the change.