All Guides·FAQ

Gameplay · 5 minutes

Joining a Public Game

Point a DevilutionX client at a DevXH gate and walk into town. The DevXH v1.0.2 client can join host:port addresses directly — stock DevilutionX 1.5.x has quirks with non-default ports (see the box below). Here's the join from the player's side, what you'll see, and how the server's idle companion works.

Everyone v1.0.2 or stock client TCP/IP & ZeroTier

What you need

Stock-client port quirk

Stock DevilutionX 1.5.5 cannot parse host:port in the join dialog — a string like us.devxh.com:6114 fails with RESOLVE: No such host is known, and a bare address always connects on the client's own port (default 6112). Workarounds on stock: use the bare hostname for 6112 gates, and for 6113/6114 gates either set [Network] Port=<port> in your diablo.ini or just use the DevXH v1.0.2 client, where host:port simply works.

Joining over TCP/IP

1

Open the multiplayer menu

Launch DevilutionX → Multiplayer → TCP/IP. In the address field, enter the gate's join address from the server list. With the DevXH v1.0.2 client, give the full host:port (e.g. us.devxh.com:6113). On a stock client, enter the bare hostname/IP and make sure your client's port matches the gate (see the quirk box above).

2

Pick the game, create your hero

The gate's game appears in the list by its advertised name (e.g. server-4821 or a custom name like My First Gate). Select it. If the host set a password, you'll be prompted — ask them for it. Choose a hero as usual and enter the world.

3

Walk into town

During the handover you may see a brief sync dialog (the world is being copied to you — usually under a second on a decent VPS). Then you're in town, and the idle host — named Server by default — will be standing by the fire, keeping the world alive.

The 4-slot truth

Every game seats four players total, and the gate itself occupies one slot as the idle host. That leaves three human slots per game. Hosting multiple groups? Run multiple gates with different --port and --name values.

Joining over ZeroTier

For ZeroTier realms there's no IP entry at all: join the realm's network first (see ZeroTier Private Realms), then in DevilutionX choose Multiplayer → ZeroTier and pick the game from the list. Everything else is identical.

Game rules of the house

Bonus: the idle bot

The same devilutionx-server binary can join another game instead of hosting — an automated companion, mule, or test client:

shell
$ ./devilutionx-server --join 192.168.1.10 \
      --hero-name Loyal --hero-class rogue \
      --data-dir ./assets --save-dir ./saves --config-dir ./cfg

The bot connects, completes the sync, and idles in town — exactly like a hosting gate's companion, just pointed at someone else's game. It works for TCP/IP addresses and ZeroTier game names alike. A version mismatch is rejected by the protocol itself, so a wrong client build can't sneak in.

Troubleshooting

SymptomFix
Game list is emptyWrong address, or the server is down. On stock clients double-check the port quirk above and journalctl -u devxh* on the host.
RESOLVE: No such host is known You typed host:port into a stock client — it can't parse the colon. Use the bare host with a matching diablo.ini port, or switch to the DevXH v1.0.2 client.
Connection times outFirewall: TCP 6112 must be reachable (or the ZeroTier realm joined & authorized).
Password prompt you can't passThe gate is private (--password). Get the password from the operator.
Sync never completesThe join retries automatically; if it keeps failing, both client and server must be compatible 1.5.x builds.
Heavy lagLockstep simulation: everyone's RTT to the server matters. Pick the nearest gate.

That's the whole ritual — the gate does the rest. May your drops be heavy and your deaths rare.