How NODERAgent updates are applied safely
What available, downloaded, activated, and rolled-back update states mean, and when a game restart is required.
On this page
NODERAgent only accepts releases prepared and signed by Nodera. Each package has an exact version and audit trail; an already published release is not rewritten. This allows you to verify what was installed and safely roll back in case of a problem.
Why doesn't the agent download any file
The service owner assigns an update channel or a specific version to the installation. NODERAgent then verifies that the offer exactly matches its license, server and installation. The downloaded package must match the expected size, checksum, and signature. A copy of a foreign package does not in itself give the right to activation.
Update states
| Status | What it means |
|---|---|
| Available | there is a newer release enabled for this installation |
| Downloading | NODERAgent is getting the specified signed package |
| Ready | the package is verified and waiting for activation; may not yet be used |
| Activating | protected file exchange in progress NODERAgent |
| Current / successful | new version running and follow-up passed |
| Returned | candidate check failed and previous working version restored |
| Failed | update was refused or incomplete; must read the reason |
Download and activation are two options
Automatic Download can prepare a release without running it. Automatic activation is a separate permission and only works when it is also enabled on a specific installation. The customer can thus have the package safely ready, but activate it only at the agreed time.
NODERAgent restart is not SCUM server restart
A regular release may restart parts of NODERAgent for a short time while the game continues to run. If a release specifically requires a SCUM server restart, activation must await a separately approved service window. The word "update" by itself never authorizes a restart of the game.
What is checked after activation
- The installation reports the new version as current.
- All 12 parts of NODERAgent are fresh and healthy again.
- NODERA-RCON confirms the secure control command.
- Server modules receive new data.
- If the release did not require a game restart, the SCUM process remained unchanged.
Current example
At the last audited rollout on 31 August 2026, the signed NODERAgent release passed the test for Test, Main, Battle Royale and the active managed installation. All four reported 12/12 healthy components and functional NODERA-RCON; SCUM servers did not restart due to agent update.
When update fails
- Check if the previous version was automatically restored.
- Do not manually copy the same package again.
- Write down the version, time and displayed safe state.
- Contact support; do not send local configuration, signatures, tokens, or the entire package.