0x04 MCP_JOINGAME

ProtocolMCP
DirectionsClient → Server and Server → Client
Used byD2DVD2XP

Joins a closed-realm game. On success the client leaves the realm and connects to the game server.

Client → Server

TypeFieldNotesConfidence
UINT16 Request ID ✅ Verified
STRING Game name ✅ Verified
STRING Password ✅ Verified

Server → Client

TypeFieldNotesConfidence
UINT16 Request ID ✅ Verified
UINT16 Game token The game's number on the game server. ✅ Verified
UINT16 Unused 0. ✅ Verified
UINT32 Game server address An IPv4 address in network byte order. ✅ Verified
UINT32 Game hash ✅ Verified
UINT32 Result ✅ Verified

Results

ValueMeaningConfidence
0x00Joined. The client closes the realm connection and connects to the game server on TCP port 4000.✅ Verified
0x29Wrong password.✅ Verified
0x2ANo such game.✅ Verified
0x2BGame is full.✅ Verified
0x2CThe character doesn't meet the game's level requirement.✅ Verified
0x6EA dead hardcore character can't join games.⚠️ Single source

Remarks

Every field is sent, even on failure. The client reads all six fields before it looks at the result, so a failure reply must still include the token, address and hash, as zeros.

The game server (D2GS) listens on port 4000, and the client can't be told to use another port. The client presents the game token and hash when it logs on to the game server.

Sources and credits

This page is written in our own words. BNETDocs is credited for its research; none of its text is copied. See Credits.

Last edited September 16, 2026 by tagban.
Edit on GitHub | Page history | Edit with Discord