Mod Updates

WardenCore is actively developed and receives regular updates with new features, bug fixes, and performance improvements. This page explains how to check for updates and install them.

Checking Your Current Version

The current WardenCore version is displayed in the bottom-left corner of the panel sidebar, shown as a version number (e.g., v1.4.0).

You can also check the version programmatically through the API:

GET /api/status

The response includes a version field with the current mod version string.

WardenCore updates are distributed as new DLL builds through the WardenCore panel at panel.wardencore.ru. When a new version is available, you download the updated mod files and replace the existing ones on your server.

Configuration is preserved

The update process only replaces the mod DLL and web assets. Your configuration files (warden_config.json, discord_config.json), database, admin list, API keys, and all other settings are stored separately and are not affected by updates.

Updating WardenCore

Check for a new version

Visit the WardenCore panel or the WardenCore Discord server to see if a new version is available. Release announcements include a changelog describing what has changed.

Download the update

Download the latest WardenCore release files from the panel. The download contains the updated mod DLL and any new or changed assets.

Stop the game server

Shut down your SCUM server before replacing mod files. Replacing files while the server is running can cause crashes or data corruption.

If you are using the SCUM Server Manager, use the Stop button. Otherwise, end the SCUMServer.exe process.

Replace the mod files

Copy the downloaded files into your WardenCore mod directory, overwriting the existing files:

SCUM/Binaries/Win64/Mods/WardenCore/

Replace only the files included in the download. Do not delete the configs folder -- it contains your settings.

Start the server

Start your SCUM server. WardenCore loads automatically and applies any internal migrations needed for the new version. Check the mod log output to confirm the new version loaded successfully.

Version Numbering

WardenCore uses Semantic Versioning (MAJOR.MINOR.PATCH):

Component	Meaning
MAJOR	Breaking changes that may require configuration updates or API changes
MINOR	New features added in a backward-compatible way
PATCH	Bug fixes and small improvements with no feature changes

For example, going from 1.3.2 to 1.4.0 means new features were added but your existing configuration still works. Going from 1.4.0 to 2.0.0 would mean breaking changes that require attention.

Configuration Migration

When a new version adds configuration fields, WardenCore handles migration automatically:

On startup, the mod checks warden_config.json for any missing fields
New fields are added with sensible defaults
The file is re-saved with the additions
A log message notes each migrated field

You do not need to manually add new configuration options after updating. The mod takes care of it.

Stale field cleanup

If a configuration field is removed in a new version (because the feature was restructured or deprecated), the mod also cleans up stale fields from your config file automatically. This keeps your configuration file clean and avoids confusion.

Common Issues

Download fails

If you cannot download the update, check that your server machine has internet access. If you are behind a corporate firewall or proxy, you may need to download the files on another machine and transfer them manually.

Update not showing

If you believe a new version has been released but do not see it, you may already be on the latest version. Compare the version number in your panel sidebar with the latest release announcement in the WardenCore Discord.

Changes not applied after update

If you replaced the files but the panel still shows the old version number, make sure you restarted the game server (not just the panel browser tab). The mod DLL is loaded when the game server starts -- refreshing the browser page does not reload the mod.

Server crashes after update

If the server fails to start after an update, verify that you downloaded the correct version for your server setup. Check the WardenCore log file for error messages. If the issue persists, restore your previous mod files from a backup and report the problem in the WardenCore Discord.