RuneScape-Dragonwilds ferment9348/dragonwilds:latest https://hub.docker.com/r/ferment9348/dragonwilds/ bridge bash false https://github.com/blckassassin/unraid-game-servers/issues https://github.com/blckassassin/unraid-game-servers RuneScape: Dragonwilds dedicated server. Native Linux binary via SteamCMD - no Proton or wine. First boot downloads about 1.5GB and settles at about 5GB. Owner ID is required - your in-game Player ID, from the bottom of the in-game Settings menu. Without it the server runs but turns away every player, so this container refuses to start and says so in the log. The fields below are written into DedicatedServer.ini on every start, so changing one and restarting takes effect. Anything else in that file is left alone. Stopping does not save. The server autosaves every 5 minutes, so a stop costs at most that. For a clean stop, have players quit out through the game menu first. GameServers: https://raw.githubusercontent.com/blckassassin/unraid-game-servers/main/templates/dragonwilds.xml https://raw.githubusercontent.com/blckassassin/unraid-game-servers/main/dragonwilds.png https://raw.githubusercontent.com/blckassassin/unraid-game-servers/main/games/dragonwilds/README.md MIT runescape dragonwilds jagex survival dedicated server ###1.1.1 (2026-09-18) - Documentation only. The image is identical to 1.1.0; there is nothing to pull. - The three-number instructions now tell you how to actually reach the container port. Unraid greys that box out for every port a template supplied, so the Edit button 1.1.0 pointed at is a dead end on a default box. The fix is to Remove the Game Port entry and add your own, which has no container port yet and so stays editable - all in the Unraid UI, no terminal and no settings to toggle. Reported from a live Unraid 6.12.24. - A template update can restore the stock Game Port entry alongside yours. Two entries then publish: yours, which works, and 7777, which nothing is listening on. Remove the restored one and Apply. - The repo's compose file publishes 8888/udp now, which the Dockerfile, this template and the README already did. ###1.1.0 (2026-09-18) - IMPORTANT, and a correction to 1.0.3 below, which had this backwards. The game port must be the SAME NUMBER in three places: the Host Port, the Container Port behind the Edit button, and Server Port. This game advertises the port the server binds, so a port mapping cannot translate it. 1.0.3 told you to change only the host side; doing that gives a world that is listed, reports ready and heartbeats fine while every player who clicks it is sent to the container port instead. On the machine this was found on, that port belonged to an ARK container. - Server Port is a normal, required field again. 1.0.3 demoted it to the advanced section on the belief that it should never be changed; that belief was wrong. - The startup log now states the three-number rule every boot instead of warning about it. The old warning fired on correct setups and could not tell a correct one from a broken one, because nothing inside a container can read its own port mapping. - New Beacon Port field, UDP 8888. The server has always bound it; it was simply undocumented. It is a compiled constant and cannot be moved. Whether clients need to reach it is still untested. - The server also binds UDP 45453 for LAN discovery. There is deliberately no field for it: it is broadcast-based and cannot work across a Docker bridge at all. Use the in-game Worlds then Direct tab with host:port on a LAN, which needs game version 0.11.1 or newer. ###1.0.3 (2026-09-17) - Server Port is no longer a field you are meant to touch, and the whole class of silent breakage it caused is gone. Unraid keeps the Container Port fixed at 7777, so the server now always binds 7777 inside the container and the port mapping above points at it. Changing the port is one number again - Game Port - and it cannot disagree with anything. - What this fixes: Game Port and Server Port were the same two words in a different order, sitting next to each other, and changing the port the obvious way set both to the new number while the Container Port stayed 7777. Docker then forwarded to a port the server never bound. The server started, the log was clean, the container showed healthy and green, and no player could reach it, with no error anywhere. - Server Port moves to the advanced section and stays at 7777. It still matters under Network Type host, where there is no mapping and it is the only port number there is. - The startup warning added in 1.0.2 now names that distinction instead of describing the three-number rule that no longer applies. ###1.0.2 (2026-09-17) - The log now warns when Server Port is not 7777. Changing the port means changing three numbers - the Host Port, the Container Port and Server Port - and Unraid hides the Container Port behind the Edit button on the Game Port row. Miss it and the server starts, logs cleanly and shows green while no player can reach it, with no error anywhere. The warning is the signal that this is the thing to check. - Host networking is now documented as the supported way to run on a non-default port. Set Network Type to host and there is one number instead of three. - Correction to 1.0.0 below: 7777/udp is not the only socket the server binds. It also binds 8888/udp, a hardcoded world settings beacon, plus an ephemeral high port. 7777 remains the only port this container publishes and the only one to forward; whether anything needs to reach 8888 is untested. ###1.0.1 (2026-09-17) - Rewrote this description. It was three long paragraphs that opened by comparing this container to other servers; it is now shorter and stands on its own. No change to the image. ###1.0.0 (2026-09-14) Initial release. - RuneScape: Dragonwilds dedicated server. The game ships a native Linux server binary, so this needs no Proton or wine - SteamCMD installs the Linux depot and the server runs directly. - Owner ID is required. It is your in-game Player ID, from the bottom of the in-game Settings menu. The container refuses to start without it, because the server itself does not: it would run, bind its port and refuse every player. - Server Name, World Name, Owner ID and both passwords are written into DedicatedServer.ini on every start, so changing one and restarting takes effect. Nothing else in that file is touched, including the ServerGuid. - Stopping the container does not save - the game's only save-on-exit path is its in-game quit flow, unreachable from outside, and it has no RCON or console. The server autosaves every 5 minutes instead, so a stop costs at most 5 minutes. Have players quit out in-game for a clean stop. Raise Unraid's container stop timeout to at least 45 seconds. - Player cap is 6. It is not a setting in this game's config file, so there is no field for it. - UDP 7777 is the only port the server binds. If something else on this box already uses it, change it here. --restart=unless-stopped About 5GB once installed, from a 1.5GB download, so allow 8GB of free space for saves and updates. Roughly 2GB of RAM plus 1GB per player, so 8GB for a full server - the cap is 6 players. The array is fine; a cache drive or SSD makes world loads and saves noticeably quicker. 7777 7777 8888 /mnt/user/appdata/dragonwilds /mnt/user/appdata/steamcmd Dragonwilds Server Standard 30 99 100 775 000