SSA Bridge

The in-game control mod for a SCUM dedicated server — 43 modules that read and change the running game. It is free, it needs no manager, and it runs on any host you can copy files to.

What it is

The bridge is a UE4SS mod that runs inside the SCUM dedicated server process. It can run any admin command, spawn items and vehicles, teleport, write chat, read live player and world state, and report kills, trades and raids as they happen — with no in-game admin account, no bot player and no game client. Everything it can do is listed in the bridge reference.

It is not a server manager and it has no interface of its own. On a standalone install you configure it by editing Mods/SSABridge/modules.json, using the modules-reference.txt the bridge writes beside it — every setting, its type, its range and its default. Driving those 43 modules from a web panel instead is what the manager is for, and that part is Premium.

What you need

• A Windows SCUM dedicated server you control the files of — your own box or a rented host that gives you file access. Nothing here works on a host that only hands you a settings panel.
• UE4SS, installed first. It is the open-source scripting runtime the bridge loads inside; this archive contains the mod alone. Put dwmapi.dll, UE4SS.dll and UE4SS-settings.ini into SCUM/Binaries/Win64/ before the mod.
• The ability to stop and start the server. The game holds these files open while it runs, so they can only be replaced with it down.

Installing it

1. Stop the server

   The running game keeps the runtime and the mod DLL open. Copying over them while it is up either fails outright or leaves you with a half-replaced install.

2. Extract the archive into SCUM/Binaries/Win64/

   The paths inside the zip are already relative to that folder, so extracting it there puts everything where it belongs. There is no installer and nothing is written outside this directory.

   <server>/SCUM/Binaries/Win64/
   └── Mods/
       └── SSABridge/
           ├── dlls/main.dll # the bridge itself
           ├── SSABridge.config.example.json # a copy to read; the real one is written on first start
           └── enabled.txt   # presence = UE4SS starts it

3. Start the server

   The bridge writes Mods/SSABridge/SSABridge.log and, once it is up, SSABridge.status.json. If neither appears, UE4SS did not load the mod — UE4SS.log in Win64/ says why, usually in one line.

4. Turn on what you want

   Every module is off by default — installing the bridge changes nothing about your server on its own. The first start writes modules.json with every module and setting at its default, and modules-reference.txt next to it explaining each one. Edit the first, read the second, restart.

Free, licensed, and what the difference is

The bridge is free and it is complete. All 43 modules, every command and every read work with the files alone — no account, no subscription, nothing held back and nothing that degrades over time.

Without a licence it introduces itself. A couple of seconds after each player joins, the bridge sends that player one line in chat naming itself and scumsa.com. With a licence, that line is not sent. That is the whole difference — no feature, no limit and no timer sits behind it.

A licence is bound to one machine and comes from your account page, on a server your plan covers: start the bridge once, copy the machineId out of Mods/SSABridge/SSABridge.status.json, paste it into Running the bridge without the manager? under that server, and put the downloaded SSABridge.license next to the mod. It is valid for 30 days. If you run the manager you never see any of this — it fetches and refreshes the licence for you, and always has.

If it expires, or you never get one, nothing stops working: the line simply appears again.

Where to go next

• Installing and configuring the bridge without a manager
• What every module can and cannot do
• The manager, which carries the bridge and configures it for you