Nephalem,
We have deployed v1.2.4 focused on join reliability, auth hardening, and cleaner diagnostics for proxied sessions.
- Critical fixed: world join could announce an internal tunnel address instead of the public endpoint in specific flows.
- High fixed: join authentication is now dynamic and validated on world join (account + game context), not static.
- Medium reviewed: web challenge host IP logic is routing-oriented and not the world-join gate.
What changed in v1.2.4
- NAT-first endpoint resolution: when NAT mode is active and a public endpoint is configured, public routing is now prioritized for announces.
- Short-lived join auth registry: token issuance now uses account + SGameId scope with TTL controls.
- Join handler validation: world entry now validates AccountId + SGameId + AuthToken, decoupled from source IP dependency.
- Real-client logging chain: canonical player identity is preserved from handshake through BGS and D3 warning logs (with safe fallback to transport endpoint).
What this means for players
- More consistent joins from proxied and mixed-network paths.
- Lower chance of connection-loss loops during game entry.
- Cleaner incident diagnostics so support can resolve session issues faster.
If you hit an issue, please report account name, UTC time, region, and a short reproduction path in Support.
— Zethrone Team
