How to update a Dragonwilds dedicated server safely
Back up your Dragonwilds world, stop the server cleanly, update Steam app 4019830, and compare the client and server versions before players return. berrybyte can run the update on every start.
RuneScape: Dragonwilds clients and dedicated servers need the same game
version. Jagex says a mismatch is likely whenever an update or hotfix ships.
The client shows its version in the top-left corner. The server prints its
version at the top of RSDragonwilds.log.
Dragonwilds 1.0 is the current public build. After a patch or hotfix, update the dedicated server the same way, then confirm the number shown by both sides. Jagex's 1.0 launch announcement covers the live client and server line.
Before the patch arrives
Tell players about the restart
Pick a quiet window. Ask everyone to finish risky fights, return to a safe place, and log out. A clean maintenance window keeps fresh progress away from the moment the process stops.
Create a backup
On berrybyte, open Backups from the server sidebar and choose Create Backup. Name it with the current version and date. The backups guide covers downloads and restores.
Self-hosters should copy RSDragonwilds/Saved/Savegames and
RSDragonwilds/Saved/Config somewhere outside the install directory.
Record the current version
Open RSDragonwilds/Saved/Logs/RSDragonwilds.log and note the version near
the top. Capture the current client version from the top-left corner too.
This gives you a useful before-and-after record.
Stop cleanly
Use Stop in the berrybyte sidebar and wait for the server to reach
Offline. With a self-hosted foreground process, send Ctrl+C and let it
exit. The power controls guide explains
when Force Kill is appropriate.
Avoid Force Kill during routine maintenance. It ends a stuck process and can lose work that has yet to reach the save file. Let the normal stop finish.
Update on berrybyte
berrybyte uses the public Linux build of Steam app 4019830. Auto Update
checks Steam as part of startup.
Open Game Settings
Sign in to the dashboard, select the server, then open Settings → Game Settings.
Enable Auto Update
Find Auto Update and switch it on. Save the setting. Leave the beta branch empty for the public build described by Jagex's dedicated-server guide.
Start the server
Press Start while the server is offline. A restart also works when the server is online because it performs a clean stop before startup. Watch Console while Steam checks the app and the world loads.
Wait for the world
Steam finishing its download only completes the file update. Keep watching
until Dragonwilds finishes loading the session. On berrybyte,
START SESSION - Success marks a successful startup.
Compare versions
Read the version near the top of the new server log. Launch Dragonwilds and compare it with the client number in the top-left corner. Exact equality is the release check.
An immediate restart can still fetch the previous server build when Steam has published the client first. Wait for the dedicated-server app to update, then start again. Repeated network and password changes will not repair version skew.
Update a self-hosted server with SteamCMD
Run SteamCMD against the same directory used for the original install. The
anonymous login and app ID come from Jagex's official guide. validate
checks installed files against Steam's current public manifest.
./steamcmd.sh +force_install_dir /path/to/dragonwilds +login anonymous +app_update 4019830 validate +quitsteamcmd.exe +force_install_dir C:\path\to\dragonwilds +login anonymous +app_update 4019830 validate +quitConfirm the process has stopped
Check the service or terminal before running SteamCMD. Updating files beneath a live process leaves the current session on old code until it exits.
Run app_update
Replace the example path with the existing server directory. Wait for SteamCMD to report success and return to the shell.
Start with logging enabled
Start Linux with ./RSDragonwildsServer.sh -log -NewConsole -Port=7777.
On Windows, use RSDragonwilds.exe -log -NewConsole -Port=7777. Keep your
configured port when it differs from the default.
Read the new log
Open RSDragonwilds/Saved/Logs/RSDragonwilds.log. Confirm the new version,
then scan startup for save, configuration, and mod errors.
Jagex's published SteamCMD command follows the current public build. Its docs do not name a supported rollback branch. A save backup can restore world data; it does not change the installed executable. Use a beta or older branch only when Jagex supplies the branch name and any required password.
Check the server after an update
The world appears in Worlds → Public
Search the exact, case-sensitive world name. Ask one player to join before the full group returns. The join guide shows the Public and Direct routes.
The expected save loaded
Check familiar buildings, storage, quest progress, and character state. Stop the server if it generated a fresh world. Restore the pre-update backup before anyone develops the replacement save.
Passwords and ownership still work
Confirm the world password accepts a normal player. The owner should open Pause → Settings → Server Management and verify owner controls. A missing Owner ID can prevent the documented server setup from working.
The log stays clean during play
Watch the console while one player moves through the world and uses recently changed content. Jagex's 0.12 update notes show why post-patch server testing matters: several dedicated-server faults needed follow-up hotfixes.
Mods after a game update
Game patches can make community loaders and plugins incompatible. Copy your mod list before maintenance. Update each component from its maintainer, and read its release notes for the new game build.
When startup fails, move server mods out of the load path and test the vanilla server against the backed-up world. Add compatible mods back in small batches. PC players who require matching client mods need the same versions and load order.
Jagex permits community modding within its Dragonwilds modding guidelines. Those rules describe acceptable projects. They do not certify that a given mod works with a new server build.
When the updated server stays missing
Start with the version numbers. Continue with the ordered can't-connect checklist after they match. It covers Owner ID, exact world-name search, the UDP game port, passwords, and mods.
SteamCMD, Owner ID, launch flags, paths, and first boot.
Back up the worldCreate, restore, browse, and download berrybyte backups.
Move or recover a saveRestore the correct .sav without changing its filename.
Dragonwilds server hostingRun the public server build with automatic update checks on start.
Frequently asked questions
How do I update a Dragonwilds server on berrybyte?
Open Settings → Game Settings, enable Auto Update, then restart the server. berrybyte checks Steam app 4019830 during startup. Wait for the server to finish loading and compare the version in the server log with the version in the top-left corner of the game client.
What is the SteamCMD app ID for the Dragonwilds dedicated server?
The dedicated-server app ID is 4019830. It supports anonymous SteamCMD login. Point app_update at the existing install directory so SteamCMD updates the current server files.
Why did my Dragonwilds server disappear after a patch?
Jagex says version mismatches commonly happen after updates and hotfixes. Read the server version at the top of its log and the client version in the top-left corner of the game. Update whichever side is behind, then try Worlds → Public again.
Should I back up before updating Dragonwilds?
Yes. Create a backup before a major update, hotfix, or mod change. A backup protects RSDragonwilds/Saved/Savegames and your configuration if the new build changes behavior or a mod fails to load.
Can I roll a Dragonwilds server back to an older build?
Jagex's public instructions only document updating app 4019830 to the current Steam build. They do not publish a rollback procedure or a supported older-build branch. Keep a pre-update backup for your world, and use another Steam branch only when Jagex publishes its name and access instructions.