How to Install EXILED Plugins on an SCP Secret Laboratory Server

To install EXILED plugins on an SCP: Secret Laboratory server, put each plugin's .dll in ~/.config/EXILED/Plugins/ (%AppData%\EXILED\Plugins\ on Windows) and any library it ships with in EXILED/Plugins/dependencies/. Restart, and the plugin writes its settings into EXILED/Configs/<port>-config.yml, named after the server's port. Plugins built for Northwood's own LabAPI go in SCP Secret Laboratory/LabAPI/plugins/global/ instead. Players install nothing.

What you are working with

SCP:SL has two plugin systems, and a plugin only loads from the folder of the system it was built for.

Since version 9, EXILED itself loads through LabAPI. That is why the Exiled.tar.gz release contains two folders, EXILED and SCP Secret Laboratory, which both belong in the same parent folder, as the EXILED installation instructions explain.

Where the folders are

Inside it:

Step 1: Before you start

• Run EXILED. On GamezServers, switch the server type to SCP:SL - Exiled in the panel. It installs the framework for you. Self hosting, use Exiled.Installer-Linux or extract the release as described above.
• Match versions. A plugin must support your EXILED version, and EXILED must support the current game version. Check the plugin's releases page.
• Back up the .config folder, or press Backup in the panel.

Step 2: Download the right file

Get the plugin from its GitHub releases page or the EXILED Discord. You need a compiled .dll, not the source code zip. If the release also contains a dependencies folder, keep it.

Step 3: Upload into the right folders

1. Stop the server.
2. Upload the plugin .dll to .config/EXILED/Plugins/.
3. Upload any dependency .dll files to .config/EXILED/Plugins/dependencies/.
4. For a LabAPI plugin, upload it to .config/SCP Secret Laboratory/LabAPI/plugins/global/ instead.
5. Start the server.

EXILED can also load new plugins without a full restart with reload plugins in the server console or Remote Admin, but a clean restart is the safer first test.

Step 4: Configure the plugin

On first start, EXILED adds a section for the plugin to EXILED/Configs/<port>-config.yml. Each plugin has at least is_enabled and usually debug, plus its own options:

example_plugin:
  is_enabled: true
  debug: false
  broadcast_message: 'Welcome to the facility'

Edit with the server stopped, keep the indentation (YAML uses spaces, never tabs), and start again. If you prefer one file per plugin, EXILED can also keep separate configs under EXILED/Configs/Plugins/<plugin>/<port>.yml.

The gotcha: configs are named after the port

EXILED names its config, translation and Remote Admin log files after the server's port, and the game keeps its own config per port too. A config written for port 7777 is ignored by a server on port 7778, which quietly generates a fresh default file instead.

This bites when you:

• Move from another host: your old 7777-config.yml uploads fine, then every plugin comes up on defaults. Rename it to your new server's port, for example 7778-config.yml, and do the same for 7777-translations.yml and the game's config/7777/ folder.
• Edit the wrong copy: after a port change you edit a file the server never reads. Check the port at the top of your panel, and edit the file with that number.

Plugin permissions

Plugin commands use EXILED permission nodes, set in EXILED/Configs/permissions.yml. Groups there match the Remote Admin groups in the game's config_remoteadmin.txt, so give your staff a Remote Admin rank first, then add plugin permissions to that group. Each plugin's page lists its permission names.

After a game update

Big SCP:SL updates often break plugins until EXILED and plugin authors catch up. Keep a backup from before the update, update EXILED with the installer or a fresh Exiled.tar.gz from its releases page, then update each plugin. If a plugin has no update yet, remove its .dll until it does.

Common problems

• Plugin does not load, no error: it is a LabAPI plugin in the EXILED folder, or the other way round. Move it.
• "Could not load file or assembly" in the console: a dependency is missing from EXILED/Plugins/dependencies/.
• Plugin loads but ignores your settings: you edited a config for a different port, or is_enabled is false.
• All plugins broke after an update: EXILED or the plugins need versions for the new game build. Restore the backup or update them.
• Config resets after editing: a YAML error, usually a tab or a wrong indent. Fix the indentation, or look for a <port>-config.yml.old backup in the same folder.

EXILED on GamezServers

On an SCP: Secret Laboratory server from GamezServers, choose the SCP:SL - Exiled type and the framework is installed for you. Plugins go up through the Files tab or SFTP (the login is in Settings), and the file manager can download a .dll straight from a GitHub link onto the server. Press Backup before every update. The basics are in how to host an SCP Secret Laboratory server.

FAQ

Where do EXILED plugins go?

In ~/.config/EXILED/Plugins/ on Linux or %AppData%\EXILED\Plugins\ on Windows, with their libraries in Plugins/dependencies/.

Where is the EXILED config file?

In EXILED/Configs/<port>-config.yml, named after your server's port. Plugins add their sections there on first start.

Do players need to install plugins?

No. Plugins run only on the server, and players join with the normal game.

Can I use LabAPI plugins and EXILED plugins together?

Yes. EXILED runs on top of LabAPI, so LabAPI plugins go in SCP Secret Laboratory/LabAPI/plugins/ and EXILED plugins in EXILED/Plugins/.