Modding
Safe SCUM configuration deployment
Preview, validation, hashes, backups and controlled writes protect SCUM configuration from blind replacement of a changed live file.
Safe configuration deployment separates preparation from writing to the live server. Administrators first read current state, edit a database draft, review the difference and only then explicitly prepare and send a specific version for application.
If the live file changed, deployment stops
Nodera uses a version-match check hash. A prepared draft is valid only for the exact source version it was based on and cannot silently overwrite a newer external change.
Safety stages in the workflow
Exact details vary by module, but the same principle protects economy, map modifiers and other supported files.
- a view-only live state record with its SHA-256
- a database draft, change preview and native-format validation
- an immutable prepared request with exact size and hash
- backup, temporary write, final verification and result audit
Where controlled deployment matters
It is most valuable for files where a mistake can affect economy, loot or server availability.
- new trader prices and purchase rules
- High Loot multipliers in GeneralZoneModifiers.json
- Notifications.json and other supported configuration requests
- Test preparation before a separate production decision
The web prepares; the agent executes
PHP never writes a remote game file directly. It creates a validated command in the authenticated queue, and NODERAgent verifies path, supported function, live hash and prepared bytes before replacement.
Each owner defines whether the change needs a reload, relog or restart. Saving a draft or applying a file never pretends that a separately required restart happened automatically.
Fewer incidents during sensitive changes
The team can see the source state, exact deployment and available backup or final hash for rollback.
Need more information?
We will show you how this feature can work on your server. Contact us or join us on Discord.
