“Join a server” can mean two different things in Dragonwilds: enter a friend’s hosted world or connect to a persistent dedicated server. Start by asking which one the host is using. The 1.0 world browser and invite-code announcement covers the first; Jagex’s server how-to covers installation and network diagnostics for the second.
Join a friend’s hosted world
Ask the host for the invite code shown in the in-game pause menu. Open the world browser and enter it there. If your platforms differ, ask the host to enable crossplay while loading the multiplayer world; the option can be chosen for each hosted session. A code from a retail key seller or giveaway is not the multiplayer invite code.
If the world still does not appear, verify that the host is online, the code was copied correctly and everyone has updated their game. These are diagnostic checks, not a claim that every connectivity error has the same cause. For the exact feature distinction, read crossplay and invitations.
Find a dedicated server
Jagex’s server guide says an operator must configure a world name and start the server before players can find it. Ask the operator for the configured name and ensure the client and server versions match. The official guide says a server that disappears from the list after a patch may simply be running an old build; compare the version shown in the server log with the client version.
If others can see a server but cannot join, Jagex specifically identifies port forwarding as a likely cause in a home-hosted setup. The default UDP port begins at 7777; a second server uses 7778, and so on. Only the operator should change router/firewall configuration. If an ISP prevents forwarding, a hosted provider or a different network arrangement may be needed.
Avoid stale fixes
An older article might prescribe a player limit or a menu sequence from 0.11. The official March guide explicitly dates its six-player figure to that version; it is not evidence of a current 1.0 maximum. Check the latest Jagex notices before treating a version-specific workaround as permanent.
Diagnose the failure by where it happens
| What you see | First checks | Who can act |
|---|---|---|
| Friend’s world not listed | Confirm the host loaded the intended world, chose crossplay for this session if needed, and shared the current invite code. | Host and guest |
| Dedicated server not listed after a patch | Compare the server log version with the game client’s version; update the server tool if they differ. | Operator |
| Server is visible but a connection fails | Verify the operator’s UDP port and home-router forwarding against the official guide. | Operator |
| An old guide gives a different menu path | Use the current 1.0 world browser and pause menu. | Guest |
Change one thing at a time and try again so you know which check mattered. The table does not imply that a visible server always has a port issue; Jagex describes forwarding as a likely cause in a home-hosted setup. Do not ask a guest to open random firewall ports on their own device or paste private server credentials into a public forum.