Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
DevXH v1.0.2 — Two Networking Fixes, One New Client
#1
DevXH v1.0.2 — Two Networking Fixes, One New Client

The doors were always open. Now every key fits every lock.

v1.0.2 is a networking-correctness release: two long-standing DevilutionX 1.5.5
bugs that directly affect DevXH gates are fixed in this fork — one on each side
of the wire. And for the first time, the fix ships as a ready-to-run
Windows client.

Fix 1 (clients): join addresses may now include a port

Stock DevilutionX 1.5.5 passes the ENTIRE join-dialog string to the hostname
resolver and always dials your client's own configured port. Consequences:
  • every
    Code:
    host:port
    join address — including everything listed on
    the website's gates table — fails with
    Code:
    RESOLVE: No such host is known
    ,
    even with perfect DNS. The colon poisons the hostname lookup.
  • a bare address resolves, but always connects on your client's port
    (default 6112) — so 6113/6114 gates were unreachable without hand-editing
    Code:
    diablo.ini
    .

The DevXH v1.0.2 client (and this source tree) splits an optional
Code:
:port
suffix from the address (backport of upstream's approach,
IPv6-bracket aware) and dials it. No port given? Falls back to your client's
own [Network] Port, exactly like vanilla 1.5.5. Type
Code:
us.devxh.com:6114
and land in Hell.

Fix 2 (servers): --port is no longer clobbered by the config file

On the server, LoadOptions() re-read
Code:
[Network] Port
from diablo.ini AFTER the command line was
parsed, silently replacing
Code:
--port 6113/6114
with the ini value
(default 6112). On a multi-gate box without a hand-seeded ini, every instance
bound 6112 and colliding instances lost the bind and exited 0 — invisible to
Code:
Restart=on-failure
. That is the exact failure seen while deploying
three gates to one box on 2026-10-04.

v1.0.2 re-applies the CLI port after LoadOptions(). Verified old-vs-new
with the packaged binary: an ini saying
Code:
Port=6112
plus
Code:
--port 6113
on the command line — the v1.0.1 binary binds
6112 (bug), the v1.0.2 binary binds 6113 (fix). Seeding
per-instance diablo.ini files is no longer required (still harmless if
you keep them).

NEW: the Windows client

First client release of the project: devxh-client-v1.0.2-win-x64.zip
(9.3 MB) contains the game executable and every DLL it needs — including
devilutionx.mpq, the engine's own free asset pack. Add a single file from
your own Diablo install (DIABDAT.MPQ, which we cannot distribute) and
you're in town. Accepts host:port joins out of the box.

Upgrading
  • Players: grab the v1.0.2 client above and joins stop guessing. Your
    heroes and saves live on your machine and carry over as usual.
  • Gate operators: replace devilutionx-server with the v1.0.2
    binary and restart your units — no config changes needed; seeded ini files keep
    working. See the handbook's upgrade section.
  • Stock 1.5.5 clients can still join: bare hostname for 6112 gates, and
    Code:
    [Network] Port=<port>
    in diablo.ini for the rest. The
    v1.0.2 client simply removes the workarounds.

The gates

All three US gates already run v1.0.2 (normal 6112, nightmare 6113, hell 6114).
See the live list: devxh.com — The Gates.

Notes from the crypt
The graveyard doors now open with any key. Take up arms.


Forum Jump:


Users browsing this thread: 1 Guest(s)