RuneScape: Dragonwilds Dedicated Server Not Showing Up

This is one of the best-documented issues in Dragonwilds. Multiple third-party hosting companies that sell Dragonwilds server rentals — Nodecraft, GameServerKings and XGamingServer among them — independently publish near-identical troubleshooting pages for it, and rather than being guesswork on their part, Jagex's own official "Dedicated Servers - A How-To Guide" and its Known Issues page document real, specific causes. Four causes account for almost every report. First, a version mismatch: Dragonwilds ships hotfixes frequently, and Jagex's own guide states that Epic Online Services "will not publish the server if there is a version mismatch with the client" — restarting the server pulls the current build and resolves most cases immediately. Second, a Steam privacy setting: Jagex's Known Issues page says plainly that "Having Steam settings set to Private will completely hide all hosted sessions in the server list, and sessions hosted by friends" — meaning a server can be running correctly and still be invisible to everyone, including the person who started it, for a reason that has nothing to do with Dragonwilds' own configuration. Third, the in-game world-name search is case-sensitive, confirmed in Jagex's guide, so a server named MyDragonServer will not appear when someone searches mydragonserver. Fourth, the OwnerID field — your own in-game Player ID, copied from the bottom of the Settings menu — has to be entered correctly in the server's config before it will broadcast at all; a blank or mistyped value is a self-hosting mistake flagged by every hosting company's own docs. A related but distinct issue is worth separating out because it looks the same from the outside: Jagex's Known Issues page also states that "Inviting a player to your Dedicated Server via Steam Invites doesn't currently connect as intended." If you were trying to pull a friend in through a Steam invite rather than having them search for your world by name, that is a known limitation, not a misconfigured server — have them use the Public tab search instead. If all of the above checks out and the server still isn't listed, hosting companies' own guides point to checking the server's boot logs for a startup error, and confirming the required ports (7777 and 7778, for a self-hosted Windows server) are open. A server that never finishes booting won't broadcast no matter how correctly everything else is set.