SCP:SL LabAPI, Plugins and Remote Admin
Drop DLLs into the LabAPI folder that already ships with the server, and keep that separate from Remote Admin ranks.
LabAPI is already in the dedicated server. You do not install the framework in order to add a plugin. You download a DLL built for LabAPI, put it in plugins, and read the console on restart. Remote Admin is a different file. It assigns ranks, not mods.
Create the server as in the install guide. Northwood support does not take plugin tickets.
Where the files go
Stop LocalAdmin. Copy the LabAPI folder before you add anything.
Windows: %AppData%\SCP Secret Laboratory\LabAPI
Linux: ~/.config/SCP Secret Laboratory/LabAPI
You should see plugins and dependencies. The plugin DLL goes in plugins. Libraries it ships go in dependencies. Another plugin listed as a dependency stays in plugins. The wiki is explicit about that split. One screenshot caption on the wiki misspells the folder. The directory they name in the previous step is dependencies.
Configs appear after the first successful start, under configs, in a folder named for the plugin. Even with no options, properties.yml can disable the plugin. The format is YAML. A console error often names the line. Renaming the broken file makes it regenerate with defaults.
Northwood says the framework has been included since dedicated-server build 14.1. A GitHub release can land before the server does. They advise waiting for the official update. If you replace the DLL anyway, it lives at SCPSL_Data/Managed/LabAPI.dll inside the dedicated-server directory. Keep the old file.
Take the DLL from the plugin's Releases, not the source archive, and read the README for the game version it targets. The catalogue they link is plugins.scpslgame.com.
Remote Admin is separate
The file is config_remoteadmin.txt. Northwood puts it in the config directory for the port: on Windows, start from %AppData%\SCP Secret Laboratory\config; on Linux, ~/.config/SCP Secret Laboratory/config, for the user that runs LocalAdmin. Do not edit the old template that is still on some Windows LocalAdmin builds. If the file misbehaves, generating a fresh config is the option they give.
A member line looks like this, including the spaces around the dash:
- 76561198000000000@steam: owner
SteamID64, @steam:, a space, then the rank name defined later in the file. Drop a space and the rank does not apply. This file does not load plugins. Mixing it up with LabAPI is the usual mix-up.
Passwords and SteamIDs from this file do not belong in a repository.
One plugin, one restart
Start again and read the first lines. The wiki wants a clean load before you add a second plugin. If joins fail with a pre-authentication "method not found" error, their page on that symptom points at an outdated plugin: remove them one at a time on a copy, or update them. They will not take a ticket for it.
If YAML stops the load, rename that plugin's config, start again, and put back one key. The round's save is not the LabAPI folder. A bad DLL comes out without deleting the match config, but copy the folder first anyway.
Offers: SCP: Secret Laboratory comparison.
Manage SCP:SL plugins from the files
Compare hosts that let you open the LabAPI folder and config_remoteadmin.txt.
Questions
Do I have to compile LabAPI?
The plugin will not turn off.
Does Remote Admin replace an admin plugin?
Sources: LabAPI README, installing plugins, configs, Remote Admin. Game support does not cover plugins: Northwood's page.
Ready to launch your SCP: Secret Laboratory server?
Here are the best SCP: Secret Laboratory hosting deals right now, promo codes included. Still unsure? Our quiz finds the ideal host for you in under 2 minutes.
SCP: Secret Laboratory — 3 Go
WinterNode
Specifications
Compatible games
Features
- ✓3 Go de RAM au minimum
- ✓CPU sans limite fixe, sous politique d'usage raisonnable
- ✓Stockage NVMe sans limite fixe, extension sur demande
- ✓Sauvegardes automatiques toutes les 12 heures
- +2 more features