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.
What you need
- DevXH client v1.0.2 (recommended) — grab the
Windows x64 client zip. It accepts
host:portjoin addresses such asus.devxh.com:6114that stock DevilutionX 1.5.5 rejects, and it bundles everything exceptDIABDAT.MPQ— add that one file from your own Diablo install. Built from the same 1.5.5 engine, so it plays on all DevXH gates just like the stock client does. - Or stock DevilutionX 1.5.x — the normal release from diasurgical/devilutionX. Works on every gate, but read the port note below before joining anything that isn't on port 6112.
- Your own game MPQs installed as usual (the DevXH client zip already bundles
devilutionx.mpq, the engine's own free asset pack). - The gate's join address from the server list — with stock clients, how you enter it depends on the port (see below).
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
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).
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.
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
- Difficulty is set by the gate. The host chooses normal, nightmare, or
hell (
--difficulty) — clients can't change it, same as any hosted game. - The game name is the door. Renamed games (
--name) show exactly that name in the lobby list. - Save data stays yours. Your hero progress saves to your own machine, as in any DevilutionX multiplayer session. The gate's idle hero persists on the server.
Bonus: the idle bot
The same devilutionx-server binary can join another game instead of
hosting — an automated companion, mule, or test client:
$ ./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
| Symptom | Fix |
|---|---|
| Game list is empty | Wrong 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 out | Firewall: TCP 6112 must be reachable (or the ZeroTier realm joined & authorized). |
| Password prompt you can't pass | The gate is private (--password). Get the password from the operator. |
| Sync never completes | The join retries automatically; if it keeps failing, both client and server must be compatible 1.5.x builds. |
| Heavy lag | Lockstep 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.