MCP_JOINGAME
| Protocol | MCP |
|---|---|
| Directions | Client → Server and Server → Client |
| Used by |
Joins a closed-realm game. On success the client leaves the realm and connects to the game server.
Client → Server
| Type | Field | Notes | Confidence |
|---|---|---|---|
UINT16 |
Request ID | ✅ Verified | |
STRING |
Game name | ✅ Verified | |
STRING |
Password | ✅ Verified |
Server → Client
| Type | Field | Notes | Confidence |
|---|---|---|---|
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
| Value | Meaning | Confidence |
|---|---|---|
0x00 | Joined. The client closes the realm connection and connects to the game server on TCP port 4000. | ✅ Verified |
0x29 | Wrong password. | ✅ Verified |
0x2A | No such game. | ✅ Verified |
0x2B | Game is full. | ✅ Verified |
0x2C | The character doesn't meet the game's level requirement. | ✅ Verified |
0x6E | A 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
- Command Center: bnetccd realm server: tested with a real Diablo II: Lord of Destruction 1.14d client
- BNETDocs, MCP_JOINGAME (client to server): documented by the original BNETDocs contributors, and edited 3 times since.
- BNETDocs, MCP_JOINGAME (server to client): documented by LordVader, and edited 3 times since.
This page is written in our own words. BNETDocs is credited for its research; none of its text is copied. See Credits.