Connecting to a Classic server

Ports

Port Transport Used for
6112 TCP The Battle.net connection itself (BNCS), for every Classic game and the chat gateway
6112 UDP Connectivity tests between server and client, and peer-to-peer game traffic for Diablo, StarCraft and Warcraft II
6112 TCP Warcraft III game hosting (the player can change this port)
Given by the server TCP The Diablo II realm (MCP). The address and port arrive in SID_LOGONREALMEX.
4000 TCP Diablo II game servers. The client cannot be told to use another port.

The first byte: choosing a protocol

Right after the TCP connection opens, the client sends one byte that tells the server which protocol follows. The server does not answer this byte.

Byte Protocol that follows Confidence
0x01 BNCS, the game protocol. Diablo II also sends this on its realm connection. ✅ Verified
0x02 BNFTP, file transfer (version-check files, icons.bni, terms of service, advertisement banners) ✅ Verified
0x03 The chat gateway (telnet), now historical ✅ Verified

A server that receives any other first byte should close the connection without replying.

How messages are framed

Different protocols in the Classic family frame their messages differently. Mixing them up is the most common mistake when writing a client or server.

Protocol Header Length counts
BNCS FF, message ID (1 byte), length (2 bytes) the whole message, including its 4-byte header
MCP (Diablo II realm) length (2 bytes), message ID (1 byte). There is no FF, and the length comes first. the whole message, including its header
W3GS (Warcraft III games) F7, message ID (1 byte), length (2 bytes) the whole message, including its header
Chat gateway Text lines ending in CR LF —

An empty BNCS message, such as a keep-alive, is exactly four bytes: FF 00 04 00.

Data types

Every number is little-endian.

Type Size Meaning
UINT8, UINT16, UINT32, UINT64 1, 2, 4, 8 bytes Unsigned integers
STRING varies Text ending in a zero byte
STRINGLIST varies Several STRINGs, ending with an empty one
FILETIME 8 bytes A Windows file time: 100-nanosecond intervals since January 1, 1601
DWORD (four-character code) 4 bytes A code such as STAR or IX86, stored as a UINT32, so its letters appear reversed on the wire: STAR is sent as 52 41 54 53 (RATS)
VOID varies Raw bytes with no further structure

Game and platform codes

Games and platforms are named by four-character codes, sent as DWORDs. Because a DWORD is little-endian, the letters go out backwards: a packet capture or hex dump of SID_AUTH_INFO from StarCraft shows 68XI and RATS, not IX86 and STAR. ✅

Read the four bytes as a little-endian number and the code comes out forwards. If your code reads them as text, reverse them.

Code Game On the wire Bytes
STAR StarCraft RATS 52 41 54 53
SEXP StarCraft: Brood War PXES 50 58 45 53
SSHR StarCraft Shareware RHSS 52 48 53 53
JSTR StarCraft (Japanese) RTSJ 52 54 53 4A
W2BN Warcraft II: Battle.net Edition NB2W 4E 42 32 57
DRTL Diablo LTRD 4C 54 52 44
DSHR Diablo Shareware RHSD 52 48 53 44
D2DV Diablo II VD2D 56 44 32 44
D2XP Diablo II: Lord of Destruction PX2D 50 58 32 44
WAR3 Warcraft III: Reign of Chaos 3RAW 33 52 41 57
W3XP Warcraft III: The Frozen Throne PX3W 50 58 33 57
Code Platform On the wire Bytes
IX86 Windows 68XI 36 38 58 49
PMAC Mac OS (PowerPC) CAMP 43 41 4D 50
XMAC Mac OS X CAMX 43 41 4D 58

The same rule applies to the product language in SID_AUTH_INFO (enUS is sent as SUne).

Where codes appear forwards or backwards as text:

  • A user's statstring in chat events starts with the game code backwards, as text: RATS, NB2W, PX3W. ✅ A Diablo II statstring must also have the right shape, or it crashes other Diablo II clients: see SID_CHATEVENT.
  • The chat gateway writes codes forwards (STAR). ✅

Text encoding and limits

  • StarCraft products (STAR, SEXP, SSHR, JSTR) send chat text as UTF-8. The other Classic games use ISO 8859-1.
  • Chat messages are limited to 224 bytes, including the terminating zero.
  • Channel names are limited to 31 characters, and account names to 15.

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 18, 2026 by tagban.
Edit on GitHub | Page history | Edit with Discord