Managing multiple SCUM servers

Managing multiple servers lets an owner operate Main, Pure, Test, Battle Royale or customer installations from one familiar interface. Every server retains a stable key, its own NODERAgent and an isolated operational context.

Data and control that remain separated

Shared navigation simplifies work, but the system checks server authorised access again for every operation.

• players, logs, current state and map data
• module settings, events and server files
• NODERAgent health, capabilities and command queue
• delegated permissions and in-game administrators for one server

Operate different server types

One team can use consistent procedures without mixing production and test decisions.

• use Main and Test for safe configuration verification
• keep a Pure vanilla policy separate from a modified Main server
• run a dedicated Battle Royale or event server
• limit a customer server to its owner and authorised team

The header selector is only the first control

The shared header chooses the active server, but a sensitive operation never trusts the submitted value alone. Nodera verifies permission, the server assignment, the unique server identifier and the compatible agent installation.

Only an authenticated agent for the correct server with the required supported function can claim a command. Result and audit remain associated with that same server context.