Server FAQ | Configuration

1. 914 Options

DroppedAndPlayerTeleport, Inventory, DroppedAndInventory, Held, DroppedAndHeld, Dropped

All options that include a players inventory also teleport.

2. What are tickets in RA?

That is the amount of chaos and mtf that can spawn for that round if tickets reach 0 that team can no longer spawn for that round.

3. How do I config the server?

Windows 10

  1. Open the Run prompt by clicking + R
  2. Type %appdata% in the Run prompt then press OK
  3. That will open File Explorer and you should be inside of C:\Users[User]\AppData\Roaming
  4. Now you need to find the SCP Secret Laboratory folder, Inside it will have another folder called Config, Open that up and go to the folder called 7777 (Or whatever the port of your server is)
  5. Inside the port folder will have all the configs, Make sure to not edit the templates, Just make new files called config_gameplay.txt & config_remoteadmin.txt then copy the stuff inside the template files and copy them over to their non-template file.

Linux

  1. Go to .config folder inside the user that you installed the SCP:SL server on
  2. Now you need to go to the SCP Secret Laboratory folder, Inside it will have another folder called Config, Open that up and go to the folder called 7777 (Or whatever the port of your server is)
  3. Inside the port folder will have all the configs, Make sure to not edit the templates, Just make new files called config_gameplay.txt & config_remoteadmin.txt then copy the stuff inside the template files and copy them over to their non-template file.

Gameplay Config

Latest Update - 10.03.2021

Server main settings

  • server_name: The servers name, You can use this Rich Text doc for cooler swagger stuff.
  • player_list_title: The ingame server name on the players list. [Default: default]
  • player_list_title_rate: [Default: default]
  • serverinfo_pastebin_id: You're servers info works from a pastebin, You can use this to make it look fancy.
  • server_ip: The servers IP address. [Default: auto]
  • max_players: Max amout of players to play on the server. [Default: 20]
  • server_tickrate: How many times the server updates per second. [Default: 60]
  • use_reserved_slots: If the server should use the UserIDReservedSlots.txt, this will allow the UserID's in the txt to join the server if it is full. [Default: true]
  • lobby_waiting_time: How many seconds players will wait until a round begins. [Default: default]
  • ipv4_bind_ip: Bind IP for IPv4. [Default: 0.0.0.0]
  • ipv6_bind_ip: Bind IP for IPv6 [Default: ::]
  • contact_email: Your email address.

Spawn settings

  • minimum_MTF_time_to_spawn: The minimum time (seconds) it should take for another wave of MTF to spawn when a respawn happens. [Default: 280]
  • maximum_MTF_time_to_spawn: The maximum time (seconds) it can take from the last wave for a new one to spawn. [Default: 350]
  • maximum_MTF_respawn_amount: The maximum amount of players that can spawn per MTF wave. [Default: 15]
  • maximum_CI_respawn_amount: The maximum amount of players that can spawn per CI wave. [Default: 15]
  • priority_mtf_respawn: Should MTF be a top priority for a respawn team? [Default: true]
  • use_crypto_rng: Enables better randomness for generation by using cryptograhic random number generator (RNG). [Default: false]

    This will use more CPU to generate numbers, Default it is set to false.

  • team_respawn_queue: Pattern in which the classes spawn at round start.

    40143140314414041340 (Designed for 20 players)

  • 0 = SCP
  • 1 = MTF (Guard)
  • 2 = Chaos
  • 3 = Scientist
  • 4 = Class-D
  • 5 = Spectator
  • 6 = Tutorial
  • smart_class_picker: Should the Smart Class Picker be enabled? [Default: true]

Player Info Range

  • player_info_range: This controls the default range that the player information text appears on clients. [Default: 10]

Respawn ticket system settings

Enables the respawn tickets system. Each NTF or CI player spawned in consumes one ticket. We recommend keeping this on for game balance! Warning: Even if you disable the system, the tickets ratio for MTF/CI will still determine their spawn chance.

  • respawn_tickets_enable: Should the respawn ticket system be enabled? [Default: true]
Ticket counts (initial)

The ratio of MTF-to-CI tickets directly determines which team has a higher chance of spawning.
The initial settings (24:14) give around 36.8% chance for the CI to spawn instead of the MTF.
The CI spawn chance can be calculated by this formula: CI_TICKETS / (MTF_TICKETS + CI_TICKETS) * 100%

  • respawn_tickets_mtf_initial_count: [Default: 24]
  • respawn_tickets_ci_initial_count: [Default: 14]
Ticket counts (events)
  • respawn_tickets_mtf_classd_cuffed_escape_count: How many tickets should be given to MTF when a classd (cuffed) escapes. [Default: 1]
  • respawn_tickets_mtf_scientist_escape_count: How many tickets should be given to MTF when a scientist escapes.[Default: 1]
  • respawn_tickets_mtf_scp_hurt_escape_count: How many tickets should be given to MTF. [Default: 1]
  • respawn_tickets_ci_classd_escape_count: How many tickets should be given to CI when a classd escapes. [Default: 1]
  • respawn_tickets_ci_scientist_cuffed_escape_count: How many tickets should be given to CI when a scientist (cuffed) escapes. [Default: 2]
  • respawn_tickets_ci_scientist_died_count: How many tickets should be given to CI when a scientist is killed. [Default: 1]
  • respawn_tickets_ci_scp_item_count: [Default: 2]

Ticket misc settings

  • respawn_tickets_mtf_scp_hurt_interval: The percentage of health an SCP must lose to trigger the 'scp_hurt' tickets. [Default: 0.25]

Stamina system settings

  • stamina_balance_use: The percentage of stamina used per second while sprinting, 0.05 = 5%, 0.33 = 33%, etc. [Default: 0.05]

NOTE: Stamina is currently only utilized on humans. 0 to disable, but this will cause weirdness with status effects and other mechanics, so we recommend keeping it on!

  • stamina_balance_immunity: The time (in seconds) that newly-spawned players can sprint without consuming stamina. Used to reduce visual artifacts. [Default: 3]
  • stamina_balance_regen_cd: The seconds that must pass before stamina starts regenerating after the player stops sprinting. [Default: 1]
  • stamina_balance_regen_speed: How fast the stamina regenerates. [Default: 1]
  • stamina_balance_walk_speed: Multiplier for human walk speed, Default speed before multiplier is 4.5 m/s. [Default: 1.2]
  • stamina_balance_sprint_speed: Multiplier for human sprint speed, Default speed before multiplier is 7 m/s. [Default: 1.05]

Random-stuff settings

-1 = random.

  • server_forced_class: Forced class on round start. [Default: -1]
  • map_seed: Force single map seed for all rounds. [Default: -1]

Misc gameplay settings

  • auto_warhead_start: Auto nuke in seconds.
  • auto_warhead_start_lock: If the warhead lever should be locked so players cannot stop autonuke. [true/false]
  • intercom_cooldown: Cooldown between intercom uses in seconds [Default: 120]
  • intercom_max_speech_time: Maximum speech time on intercom in seconds [Default: 20]
  • auto_round_restart_time: After how many rounds should the server automatically restart? [Default: 10]
  • friendly_fire: Should Friendly Fire be enabled? [Default: false]
  • friendly_fire_multiplier: 0.1-2 How big is friendly fire damage multiplier? [Default: 1]
  • warhead_tminus_start_duration: How long does it take to detonate the Warhead in seconds? [Default: 90]
  • human_grenade_multiplier: How much damage from the grenade is dealt to human classes? [Default: 0.7]
  • scp_grenade_multiplier: How much damage from the grenade is dealt to SCP? [Default: 1]
  • lock_gates_on_countdown: Should gates be locked (non-closable) while there's a Warhead countdown? [Default: true]
  • isolate_zones_on_countdown: Should gates get closed while there's a Warhead countdown? [Default: false]
  • open_doors_on_countdown: Should all inside-facility doors get opened when there's a Warhead countdown? Gates are overriden by parameter above [Default: true]
  • keep_items_after_escaping: Should players keep their items after respawning as an addition to current loadout? [Default: true]
  • allow_playing_as_tutorial: Should Tutorial be available using forceclass? [Default: true]
  • disable_decontamination: Should decontamination get disabled? [Default: false]
  • 096_destroy_locked_doors: Give 096 access to destroy locked doors? [Default: true]
  • no_holidays: Should holiday specials be disabled? (Halloween, Christmas etc.) [Default: false]
  • allow_disarmed_interaction: Should disarmed players be able to interact with doors? [Default: false]
  • 914_mode: Take a look at the top of the page for all available modes [Default: default]
  • sinkhole_slow_amount: By how much units should 106 Sinkhole slow players down? [Default: 30]
  • sinkhole_spawn_chance: What is the chance of sinkhole spawn in percent? [Default: 0]
  • disconnect_drop: Should disconnected players automatically drop their items? [Default: true]
  • ragdoll_cleanup_time:Time in seconds till ragdolls are removed. Set below 1 to disable. [Default: 0]
  • end_round_on_one_player: Should round end when there's only one player on the server? [Default: false]
  • ci_on_start_percent: Chance for CI to spawn at the beginning of a round. [Default: 10]
  • afk_time: How many seconds someone is AFK sitting in their spawn location before they are kicked when a round started. Set to 0 to disable. [Default: 90]
  • constantly_check_afk: Should the AFK system constantly check if someone is AFK during a round? [Default: false]

Pocket Dimension Settings

  • pd_exit_count: How many valid exits appear in Pocket Dimension? [Default: 2]

Disarmer settings

  • mtf_can_cuff_researchers: Can MTF cuff Researchers? [Default: true]
  • ci_can_cuff_class_d: Can CI cuff Class D? [Default: true]
  • cuffed_escapee_change_team: Should cuffed Class D that escapes become MTF? [Default: true]

Spawn Protect settings

  • spawn_protect_disable: If spawn protection should be disabled. [Default: true]
  • spawn_protect_time: How long spawn protection should last. [Default: 30]
  • spawn_protect_team: [Default: [1, 2]]

Team ID's

  • 0 = SCP
  • 1 = MTF
  • 2 = CHI (Chaos Insurgency)
  • 3 = RSC (Research)
  • 4 = CDP (Class-D Personnel)
  • 5 = RIP (Spectator)
  • 6 = TUT
  • spawn_protect_allow_dmg: If players that are in spawn protection should be allowed todo damages. [Default: true]

Auto Event Broadcast settings

  • auto_warhead_broadcast_enabled: Should a broadcast be sent when the auto warhead is engaged? [Default: false]
  • auto_warhead_broadcast_message: [Default: "The Alpha Warhead is being detonated"]
  • auto_warhead_broadcast_time: [Default: 10]
  • auto_warhead_detonate_broadcast: [Default: "The Alpha Warhead has been detonated now"]
  • auto_warhead_detonate_broadcast_time: [Default: 10]
  • auto_decon_broadcast_enabled: Should a broadcast be sent when LCZ is decontaminated? [Default: false]
  • auto_decon_broadcast_message: [Default: "Light Containment Zone is now decontaminated"]
  • auto_decon_broadcast_time: [Default: 10]

Grenades chaining options

-1 to unlimited, 0 to disable chain reaction

  • grenade_chain_limit: Maximum amount of grenades that can be activated by a single grenade [Default: 10]
  • grenade_chain_length_limit: Maximum length of grenades chain [Default: 4]

Security & Anticheat (default settings are good enough in most cases)

Please type !private in your server console, if your server is verified, but you want to keep it hidden from the list. Type !public to make it public again.

  • online_mode: [Default: true]
  • ip_banning: [Default: true]
  • enable_whitelist: [Default: false]
  • forward_ports: [Default: true]
  • enable_query: [Default: false]
  • query_port_shift: [Default: 0]
  • query_use_IPv6: [Default: true]
  • administrator_query_password: [Default: none]
  • connections_delay_time: [Default: 5]
  • enable_sync_command_binding: [Default: false]
  • ratelimit_kick: [Default: true]
  • same_account_joining: [Default: false]
  • anticheat_console_output: [Default: false]
  • enable_fast_round_restart: [Default: true]
  • fast_round_restart_delay: [Default: 3.2]

Enables challenge during preauthentication

  • preauth_challenge [Default true]

Reply - prevents from flooding server with preauth requests from spoofed IP addresses MD5 or SHA1 - prevents from flooding with preauth requests from legitimate IP addresses as well. Requires additional time to join the server.

  • preauth_challenge_mode: [Default: reply]
  • preauth_challenge_base_length: [Default: 10]
  • preauth_challenge_time_window: [Default: 12]
  • preauth_challenge_clean_period: [Default: 4]

Only for MD5 and SHA1 challenges (higher value = longer time required to join the server)

  • preauth_challenge_secret_length: [Default 2]

This enforces the player to be using same IP address to connect to the game and authenticate. Enabling this blocks proxies. Not enforced if player joined from IPv4 and authenticated from IPv6 or viceversa. Situations with combinating IPv4 and IPv6 addresses are being checked on central servers after authentication (only for servers on public list).

  • enforce_same_ip: [Default true]
  • no_enforcement_for_local_ip_addresses: [Default true]

This enforces that the IP address used to connect to the game and authenticate must be assigned to the same Internet Service Provider (ISP). Works only on servers on the public list. This is less restrictive that "enforce_same_ip" and blocks most of the proxies.

  • enforce_same_asn: [Default true]

Connections ratelimiting Ratelimit time windows define how often user with the same IP/UserID can initialize new connection (once per X seconds).

  • enable_ip_ratelimit: [Default true]
  • enable_userid_ratelimit: [Default true]
  • ip_ratelimit_window: [Default 3]
  • userid_ratelimit_window: [Default 5]

Please refrain from changing any of these settings without enough knowledge.

Item limits

Ammo settings in this config are sorted as [X, Y, Z]

  • X = 5.56mm (E-11-SR)
  • Y = 7.62mm (Logicer, MP7)
  • Z = 9mm (P90, COM-15)
Default ammo that each class gets on respawn
  • class_d_personnel_defaultammo: Default: [0, 0, 0]
  • nine_tailed_fox_scientist_defaultammo: Default: [120, 20, 20]
  • scientist_defaultammo: Default: [0, 0, 0]
  • chaos_insurgency_defaultammo: Default: [0, 100, 0]
  • nine_tailed_fox_lieutenant_defaultammo: Default: [80, 0, 50]
  • nine_tailed_fox_commander_defaultammo: Default: [120, 0, 100]
  • nine_tailed_fox_cadet_defaultammo: Default: [40, 0, 100]
  • tutorial_defaultammo: Default: [0, 0, 0]
  • facility_guard_defaultammo: Default: [0, 35, 0]
Ammo limits, values from 0 to 65.5k, where 0 = unlimited.
  • class_d_personnel_ammolimit: Default: [80, 70, 50]
  • nine_tailed_fox_scientist_ammolimit: Default: [160, 100, 200]
  • scientist_ammolimit: Default: [80, 70, 50]
  • chaos_insurgency_ammolimit: Default: [80, 200, 100]
  • nine_tailed_fox_lieutenant_ammolimit: [160, 100, 200]
  • nine_tailed_fox_commander_ammolimit: [160, 100, 200]
  • nine_tailed_fox_cadet_ammolimit: Default: [160, 100, 200]
  • tutorial_ammolimit: Default: [160, 100, 200]
  • facility_guard_ammolimit: Default: [160, 100, 200]
Item limits - values range from 0 to 8.

Values of 0 are NOT unlimited and will prevent item pickups of that type entirely! The inventory can hold a max of 8 items, so a limit of 8 is effectively unlimited.

  • itemlimit_keycard: [Default: 3]
  • itemlimit_medical_item: [Default: 3]
  • itemlimit_weapon: [Default: 2]
  • itemlimit_grenade: [Default: 3]
  • itemlimit_scp_item: [Default: 3]

Friendly Fire Detector

How do I disable FF Detector? Check the Server FAQ!
If Friendly Fire is disabled, there is no need to disable the Detector too.

Action is performed if someone either kills enough teammates OR deals enough damage to teammates.
Detectors priority:
Respawn (kill) -> Window (kill) -> Life (kill) -> Round (kill) -> Respawn (damage) -> Window (damage) -> Life (damage) -> Round (damage)
Set kills or damage to 0 to disable that threshold.

Actions:

  • kill
  • kick
  • ban
  • noop (no operation - do nothing, eg. to enable logging)

Damage dealt AFTER round end is ignored.

  • ff_detector_global_broadcast_seconds: For how long should the message be displayed on the Broadcast? [Default: 5]
  • ff_detector_global_adminchat_seconds: For how long should the message be displayed on Admin Chat? [Default: 6]
  • [Default: 6, Min: 4, Max: 25]
  • ff_detector_classD_can_damage_classD: If enabled Class D personnel can damage or kill other Class D personnel without being punished for it [Default: false]
  • ff_detector_webhook_url: If set to "none" then the webhook for cheaters reporting will be used [Default: none]
Per round
  • ff_detector_round_enabled: Decides if Per Round FF detector should be enabled. [Default: true]
  • ff_detector_round_kills: How much kills per round player has to make to trigger the detector. [Default: 6]
  • ff_detector_round_damage: How much damage per round player has to deal to trigger the detector. [Default: 500]
  • ff_detector_round_action: Action made after triggering the detector [Default: ban]
  • ff_detector_round_ban_time: For how long should the player be banned. Used only if the action is set to ban
  • [Default: 24h, Formats: s, m, h, d, M (months), y]
  • ff_detector_round_bankick_reason: Message displayed to player after getting kicked/banned
  • ff_detector_round_kill_reason: Message displayed to player after being killed for teamkilling
  • ff_detector_round_adminchat_enable: Should admin chat messages be sent [Default: false]
  • ff_detector_round_adminchat_message: Message sent to admin chat [Note: %nick - Player nickname]
  • ff_detector_round_broadcast_enable: Should broadcast messages be sent [Default: true]
  • ff_detector_round_broadcast_message: Broadcast message sent to players [Note: %nick - Player nickname]
  • ff_detector_round_webhook_report: Should messages be sent using Discord Webhook? [Default: true]
Per life - Resets on respawn
  • ff_detector_life_enabled: Decides if Per Life FF detector should be enabled. [Default: true]
  • ff_detector_life_kills: How much kills per life player has to make to trigger the detector [Default: 4]
  • ff_detector_life_damage: How much damage per life player has to deal to trigger the detector [Default: 300]
  • ff_detector_life_action: Action made after triggering the detector [Default: ban]
  • ff_detector_life_ban_time: For how long should the player be banned. Used only if the action is set to ban
  • [Default: 24h, Formats: s, m, h, d, M (months), y]
  • ff_detector_life_bankick_reason: Message displayed to player after getting kicked/banned
  • ff_detector_life_kill_reason: Message displayed to player after being killed for teamkilling
  • ff_detector_life_adminchat_enable: Should admin chat messages be sent [Default: false]
  • ff_detector_life_adminchat_message: Message sent to admin chat [Note: %nick - Player nickname]
  • ff_detector_life_broadcast_enable: Should broadcast messages be sent [Default: true]
  • ff_detector_life_broadcast_message: Broadcast message sent to players [Note: %nick - Player nickname]
  • ff_detector_life_webhook_report: Should messages be sent using Discord Webhook? [Default: true]
In a specified time window
  • ff_detector_window_enabled: Decides if specified time window FF detector should be enabled. [Default: true]
  • ff_detector_window_seconds: For how long is the window active [Default: 180]
  • ff_detector_window_kills: How much kills in specified time window player has to make to trigger the detector [Default: 3]
  • ff_detector_window_damage: How much damage per life player has to deal to trigger the detector [Default: 250]
  • ff_detector_window_action: Action made after triggering the detector [Default: ban]
  • ff_detector_window_ban_time: For how long should the player be banned. Used only if the action is set to ban
  • [Default: 16h, Formats: s, m, h, d, M (months), y]
  • ff_detector_window_bankick_reason: Message displayed to player after getting kicked/banned
  • ff_detector_window_kill_reason: Message displayed to player after being killed for teamkilling
  • ff_detector_window_adminchat_enable: Should admin chat messages be sent [Default: false]
  • ff_detector_window_adminchat_message: Message sent to admin chat [Note: %nick - Player nickname]
  • ff_detector_window_broadcast_enable: Should broadcast messages be sent [Default: true]
  • ff_detector_window_broadcast_message: Broadcast message sent to players [Note: %nick - Player nickname]
  • ff_detector_window_webhook_report: Should messages be sent using Discord Webhook? [Default: true]
In a specified time window AFTER RESPAWN
  • ff_detector_spawn_enabled: Decides if specified time window after respawn FF detector should be enabled. [Default: true]
  • ff_detector_spawn_window_seconds: For how long is the window active [Default: 120]
  • ff_detector_spawn_kills: How much kills in specified time window player has to make to trigger the detector [Default: 2]
  • ff_detector_spawn_damage: How much damage per life player has to deal to trigger the detector [Default: 180]
  • ff_detector_spawn_action: Action made after triggering the detector [Default: ban]
  • ff_detector_spawn_ban_time: For how long should the player be banned. Used only if the action is set to ban
  • [Default: 48h, Formats: s, m, h, d, M (months), y]
  • ff_detector_spawn_bankick_reason: Message displayed to player after getting kicked/banned
  • ff_detector_spawn_kill_reason: Message displayed to player after being killed for teamkilling
  • ff_detector_spawn_adminchat_enable: Should admin chat messages be sent [Default: false]
  • ff_detector_spawn_adminchat_message: Message sent to admin chat [Note: %nick - Player nickname]
  • ff_detector_spawn_broadcast_enable: Should broadcast messages be sent [Default: true]
  • ff_detector_spawn_broadcast_message: Broadcast message sent to players [Note: %nick - Player nickname]
  • ff_detector_spawn_webhook_report: Should messages be sent using Discord Webhook? [Default: true]

Custom Whitelist

Enable this ONLY if you use plugin or modification that provides custom whitelist. This is only to mark the server on the public list as using a whitelist. More information can be found in Verified Server Rules. If your server is not on the public list - ignore this.

  • custom_whitelist: [Default: false]

Enable this ONLY if you use plugin or modification that restricts access to the server (other than whitelist, eg. password). This is only to mark the server on the public list as using access restriction. More information can be found in Verified Server Rules. If your server is not on the public list - ignore this.

  • server_access_restriction: [Default: false]

Port Queue

For nondedicated servers only

port_queue:
- 7777
- 7778
- 7779
- 7780
- 7781
- 7782
- 7783
- 7784

Enabling this will automatically ban IP of players on the server that receives a Global Ban by a Global Moderator. (Defaults to false)

  • gban_ban_ip: [Default: default (true)]

  • ban_nickname_maxlength: [Default: default]

  • ban_nickname_trimunicode: [Default: default]

Nickname filtering, using regex

  • nickname_filter: [Default: default]
  • nickname_filter_replacement: [Default: default]

Administrative actions broadcast options

  • broadcast_kicks: Should kick messages get announced to all players? [Default: false]
  • broadcast_kick_text: Text of a kick message [Note: %nick% for player nickname]
  • broadcast_kick_duration: How long is kick message visible in seconds? [Default: 5]
  • broadcast_bans: Should ban messages get announced to all players? [Default: true]
  • broadcast_ban_text: Text of a ban message [Note: %nick% for player nickname]
  • broadcast_ban_duration: How long is kick message visible in seconds? [Default: 5]

Server idle mode

  • idle_mode_enabled: Is Idle mode enabled? [Default: true]
  • idle_mode_time: How long should server be awake before going idle? [Default: 5000]
  • idle_mode_preauth_time: [Default: 30000]
  • idle_mode_tickrate: [Default: 1]

Player report

  • report_send_using_discord_webhook: Should the report system be enabled? [Default: false]
  • report_discord_webhook_url: Webhook URL to send the reports [Default: PleaseSetWebhookUrlHere]
  • report_username: What should be the name of webhook? [Default: Cheater Report]
  • report_avatar_url: [Default: default]
  • report_color: Color of the report in decimal [Default: 14423100]
  • report_server_name: Server name in the report [Default: My SCP:SL Server]
  • report_header: Header of the report [Default: Player Report]
  • report_content: Content of the report [Default: Player has just been reported.]

Restart options

Requires LocalAdmin or a fully compatible tool.
  • restart_after_rounds: You can set autorestart of the server after a specified amount of rounds (0 - disabled). [Default: 0]
  • full_restart_rejoin_time Amount of time after client should rejoin after a full server restart, Adjust depending on your server restart time. [Default: 25]

Geoblocking

If your server is on the public list, please refer to Verified Server Rules for more details.
Modes: none, whitelist, blacklist

  • geoblocking_mode: Which mode should geoblocking use? [Default: none]
  • geoblocking_ignore_whitelisted: If enabled, players on the whitelist are able to ignore geoblocking. [Default: true]

Use ISO country codes, eg. PL, US, DE

geoblocking_whitelist:
- AA
- AB
- AC

geoblocking_blacklist:
- AA
- AB
- AC


Remote Admin Config

Game Staff Access

  • enable_staff_access: Should Secret Lab development staff be able to use the Remote Admin? [Default: true]
  • enable_manager_access: Should Secret Lab CEO and managers be able to use Remote Admin? (We do not abuse our powers) [Default: true]
  • enable_banteam_access: Allow remote admin access for the banning team, to allow them searching and fighting cheaters globally [Default: true]
  • enable_banteam_reserved_slots: Enable reserved slots for the banning team (they are restricted by reserved slots limit set in the gameplay config) [Default: true]
  • enable_banteam_bypass_geoblocking: Allow the banning team to bypass georestrictions on the server [Default: true]

Assigning Roles to Players

UserID format is SteamId64Here@steam or DiscordUserIDHere@discord. You can get SteamID64 here and DiscordUserID here.

Members:
- #################@steam: owner
- #################@steam: admin
- #################@discord: moderator

Remember to remove #################@ and other placeholders that are not used! You will encounter errors

Creating Roles

  • badge - Displayed name of the role
  • color - Color of the Badge. Use none to disable badge. (List of Colors below)
  • cover - This local badge is more important than a global badge and will cover it
  • hidden - This local badge is hidden by default (Still can use "hidetag" and "showtag" commands in-game)
  • kick_power - Power for kicking and banning that the member of this group has (0 to 255)
  • required_kick_power - Required kick power to kick or ban a member of this group (0 to 255)

Default Roles:

owner_badge: Owner
owner_color: red
owner_cover: true
owner_hidden: false
owner_kick_power: 255
owner_required_kick_power: 255

admin_badge: Admin
admin_color: red
admin_cover: true
admin_hidden: false
admin_kick_power: 1
admin_required_kick_power: 2

moderator_badge: Moderator
moderator_color: silver
moderator_cover: true
moderator_hidden: false
moderator_kick_power: 0
moderator_required_kick_power: 1

Roles List

Roles:
- owner
- admin
- moderator

List of Colors
Color Sample Restricted
gold █████ Yes
teal █████ Yes
blue █████ Yes
purple █████ Yes
light_red █████ Yes
silver_blue █████ Yes
police_blue █████ Yes
pink █████
red █████
brown █████
silver █████
light_green █████
crimson █████
cyan █████
aqua █████
deep_pink █████
tomato █████
yellow █████
magenta █████
blue_green █████
orange █████
lime █████
green █████
emerald █████
carmine █████
nickel █████
mint █████
army_green █████
pumpkin █████

What are restricted colors? They are used in Game Staff badges, if you try to use them on your own server - they will not be visible.

Permissions

Default Permissions as on 10/14/2021.

Permissions:
- KickingAndShortTermBanning: [owner, admin, moderator]
- BanningUpToDay: [owner, admin, moderator]
- LongTermBanning: [owner, admin]
- ForceclassSelf: [owner, admin, moderator]
- ForceclassToSpectator: [owner, admin, moderator]
- ForceclassWithoutRestrictions: [owner, admin]
- GivingItems: [owner, admin]
- WarheadEvents: [owner, admin, moderator]
- RespawnEvents: [owner, admin]
- RoundEvents: [owner, admin, moderator]
- SetGroup: [owner]
- GameplayData: [owner, admin]
- Overwatch: [owner, admin, moderator]
- FacilityManagement: [owner, admin, moderator]
- PlayersManagement: [owner, admin]
- PermissionsManagement: [owner]
- ServerConsoleCommands: []
- ViewHiddenBadges: [owner, admin, moderator]
- ServerConfigs: [owner]
- Broadcasting: [owner, admin, moderator]
- PlayerSensitiveDataAccess: [owner, admin, moderator]
- Noclip: [owner, admin]
- AFKImmunity: [owner, admin]
- AdminChat: [owner, admin, moderator]
- ViewHiddenGlobalBadges: [owner, admin, moderator]
- Announcer: [owner, admin]
- Effects: [owner, admin]
- FriendlyFireDetectorImmunity: [owner, admin, moderator]
- FriendlyFireDetectorTempDisable: [owner, admin]

Allows running central server commands (they are prefixed with "!") using "sudo"/"cron" command in RA (requires ServerConsoleCommands permission).

Don't turn on unless you fully trust all people with this permission, they needs to run that commands from RA and you know what are you doing

  • allow_central_server_commands_as_ServerConsoleCommands: [Default: false]

Should the GUI-Based RA use the predefined ban templates below?

  • enable_predefined_ban_templates: [Default: true]

Here you can define ban templates for your staff members to use in-game. This can always be overridden by choosing the "Custom" ban tab

FORMAT: - [Duration in seconds, Reason]

Note The reason cannot contain any commas or it will break the parsing!

PredefinedBanTemplates:

  • [0, Consider this a warning!]
  • [3600, Mic Spamming]
  • [86400, Team Killing (Minor Offence)]
  • [604800, Team Killing (Major Offence)]
  • [1577000000, Abusing Exploits]

Detailed info about permission nodes (Click me)

KickingAndShortTermBanningAllows staff to kick players and do short term banning.

BanningUpToDay Allows staff to ban players up to a day.

LongTermBanning Allows staff to ban players for any time.

ForceclassSelf Allows staff to force-class themself.

ForceclassToSpectator Allows staff to force-class players into spectator.

ForceclassWithoutRestrictions Allows staff to force-class anyone without restrictions.

GivingItems Allows staff to give items to themself/players.

WarheadEvents Allows staff to active warhead events.

RespawnEvents Allows staff to use respawn events for CI & MTF.

RoundEvents Allows staff to use round events such as lockround, Lobbylock, etc.

SetGroup Allows staff to use the setgroup command, Do not give this to everyone. The setgroup command can set players rank and give them staff rank.

GameplayData Allows staff to see players gameplay data in the "Player spec. info" part of RA.

Overwatch Allows staff to set themself to overwatch mode, Usefully for watching sus players that may be breaking the rules.

FacilityManagement Allows staff to break the server use the Door management part of the RA panel.

PlayersManagement Allows staff to use the Player mgmt part of RA panel.

PermissionsManagement Type "PM" into RA console to read about it.

ServerConsoleCommands Allows staff to execute commands in LocalAdmin console, Do NOT give this permission to everyone.

ViewHiddenBadges Allows staff to see hidden badges of other players/staff, Not studio staff.

ServerConfigs Allows staff to use the Server configs section of RA panel.

Broadcasting Allows staff to make broadcasts.

PlayerSensitiveDataAccess Allows staff to see players IP/auth's.

Noclip Allows staff to give themself/players noclip, Use noclip with left alt.

AFKImmunity Allows staff to be immune to auto-afk.

AdminChat Allows staff to use adminchat. [Type @ in RA console or debug console.]

ViewHiddenGlobalBadges Allows staff to view hidden g-badges.

Announcer Allows staff to use the cassie command.

Effects Allows staff to use effects.

FriendlyFireDetectorImmunity Allows staff to be immune to FF detector.

FriendlyFireDetectorTempDisable Allows staff to temporally disable FF detector.

RA PASSWORD REMOVED

RA Password section is removed from this FAQ due to it being forcefully disabled for a good reason, You cannot enable it nor should you.

Some stuff here was pulled from the SCP:SL Wiki, If you have any questions or concerns or find a typo you can either join our discord server here or send a email at scpsl.faq@gmail.com