User Profile

A MCP_GAMELIST packet with a 0x00 Game name indicates the end of the list.

The D2XP client sends this packet approximately every 15 seconds while the "Join Game" tab is focused. The request id is incremented by 0x01 for each subsequent MCP_GAMELIST (this is the same request id that is used by MCP_CREATEGAME and MCP_JOINGAME).

• Possibly a bug with the D2XP client, but this packet appears to be sent twice on the initial focus.

D2XP client sends 0x0800 for the second dword, not 0x00.

For D2XP: The game state, uptime, type, sub type, provider, and ladder type are all set to 0x00, Only the game name, password, and description are sent. In addition, the server does not appear to respond to this packet.

The server doesn't appear to respond with this packet when using the D2XP client.

The comment about the request id being incremented by 0x02 is misstated. The request id is incremented by 0x01 for each MCP_CREATEGAME request and 0x01 for each MCP_JOINGAME request. For example, if the MCP_CREATEGAME request fails, the subsequent request id would be 0x03.