What NODERAgent does and how to read its status
A clear explanation of NODERAgent, its 12 components, feature availability, and the states from submitting an action to receiving its result.
On this page
NODERAgent is a secure connection between Nodera administration and one SCUM server. It collects necessary states, reads supported game logs, prepares data for modules and performs only permitted server actions. Thanks to it, the web administration does not need to know Windows passwords or connect directly to the game server.
What NODERAgent provides
- server process status and regular contact with Nodera,
- overview of online players, squads and supported game data,
- reading and processing SCUM logs for administration and automation,
- safe execution of enabled commands via local NODERA-RCON,
- backups and selected server files according to the available function,
- signed updates by NODERAgent himself.
Why is it showing 12/12
Full Agent divides the work into 12 separately monitored parts. Each is responsible for a specific type of work, for example communication, player data or a selected type of log. A value of 12/12 means that all expected parts have recently confirmed a healthy state.
| Status | Meaning for administrator |
|---|---|
| 12/12 | all parts are fresh and healthy; still verify the specific feature you want |
| 11/12 or less | one or more parts need attention; detail will show which |
| Agent offline or stale contact | Nodera has no recent heartbeat and write actions should be safely blocked |
Why one function may be unavailable
NODERAgent reports which specific features the given installation currently supports. For example, a live map, secure chat, quest management or game admin registration may require a certain version, setting and healthy part of the agent. If the condition is missing, the button is hidden or disabled so that Nodera does not pretend to perform the action.
Do not work around an unavailable feature by direct RCON, editing server files, or the general console. First check the license, version, agent status and correct server.
What happens after clicking on a server action
- The administration will verify your authorization, selected server and input values.
- Nodera will safely list a specific action with limited validity.
- NODERAgent will pick it up and execute it on its server.
- It sends back the result and the corresponding module refreshes the displayed state.
How to read the result
| Status | What to do |
|---|---|
| Successful | the desired result has been confirmed; verify it also in module |
| Failed | open a secure error message and correct the cause |
| Expired or cancelled | the action will no longer be performed; after checking, a new one can be created |
| The result is not clear | do not repeat the action automatically, first find out the real status |
Role of NODERA-RCON
NODERA-RCON is NODERAgent's local connection to its SCUM server. It is not publicly open to the web or to the customer as a separate remote password. The administration sends safely named actions through NODERAgent, which executes them locally and returns the result.
Current example
When audited on 1 September 2026, the main SCUM server had fresh contact, all 12 NODERAgent components and verified local NODERA-RCON. Player data was scheduled to refresh every 5 seconds and world overview every 30 seconds; this is a target interval, not a guarantee of immediate display in every browser.