Warcraft III: logon to chat
![]()
How Warcraft III connects, passes the version check, logs on with NLS and joins a channel. Checked against a real The Frozen Throne 1.27b client.
| # | Client | Server | What happens | Confidence | |
|---|---|---|---|---|---|
| 1 | 0x01 |
→ | Protocol byte: BNCS follows. | ✅ Verified | |
| 2 | SID_AUTH_INFO |
→ | Names the game (WAR3 or W3XP) and version byte (0x1B for 1.27b). |
✅ Verified | |
| 3 | ← | SID_PING |
✅ Verified | ||
| 4 | ← | SID_AUTH_INFO |
Logon type 0x02 (NLS), the version check, and the 128-byte signature, which must be present. |
✅ Verified | |
| 5 | SID_AUTH_CHECK |
→ | The Frozen Throne sends two CD keys. | ✅ Verified | |
| 6 | ← | SID_AUTH_CHECK |
✅ Verified | ||
| Files, downloaded over BNFTP version 2 on separate connections | |||||
| 7 | SID_GETFILETIME |
→ | Terms of service and bnserver-WAR3.ini, one request each. |
✅ Verified | |
| 8 | ← | SID_GETFILETIME |
✅ Verified | ||
| 9 | SID_GETICONDATA |
→ | ✅ Verified | ||
| 10 | ← | SID_GETICONDATA |
Usually icons-WAR3.bni. |
✅ Verified | |
| Only when the player creates a new account | |||||
| 11 | SID_AUTH_ACCOUNTCREATE |
→ | Salt and verifier. | ✅ Verified | |
| 12 | ← | SID_AUTH_ACCOUNTCREATE |
0x00 created. |
✅ Verified | |
| Logging on | |||||
| 13 | SID_AUTH_ACCOUNTLOGON |
→ | Client public key A. | ✅ Verified | |
| 14 | ← | SID_AUTH_ACCOUNTLOGON |
Salt and server public key B. Always 72 bytes. | ✅ Verified | |
| 15 | SID_AUTH_ACCOUNTLOGONPROOF |
→ | Client proof M1. | ✅ Verified | |
| 16 | ← | SID_AUTH_ACCOUNTLOGONPROOF |
Status and server proof M2: exactly 24 bytes. | ✅ Verified | |
| Entering chat | |||||
| 17 | SID_NETGAMEPORT |
→ | The port it hosts games on. | ✅ Verified | |
| 18 | SID_ENTERCHAT |
→ | ✅ Verified | ||
| 19 | ← | SID_ENTERCHAT |
The client accepts a realm-style name such as Name@Realm. |
✅ Verified | |
| 20 | SID_WARCRAFTGENERAL |
→ | Tournament status and the ladder map list. | ✅ Verified | |
| 21 | ← | SID_WARCRAFTGENERAL |
✅ Verified | ||
| 22 | SID_FRIENDSLIST |
→ | ✅ Verified | ||
| 23 | ← | SID_FRIENDSLIST |
✅ Verified | ||
| 24 | SID_NEWS_INFO |
→ | ✅ Verified | ||
| 25 | ← | SID_NEWS_INFO |
✅ Verified | ||
| 26 | SID_JOINCHANNEL |
→ | Flags 0x01 (first join). |
✅ Verified | |
| 27 | ← | SID_CHATEVENT |
✅ Verified | ||
Remarks
Only NLS works. An unmodified Warcraft III won't use the older X-SHA-1 logon: if the server offers logon type 0x00, the client disconnects before the version check.
The server signature. Under NLS, Warcraft III checks the 128-byte signature in SID_AUTH_INFO against a key built into the game. No server other than Blizzard's can produce a valid one, so connecting to any other server requires a client modification that skips the check. This site doesn't host or link one. The server simply has to include the 128 bytes; zeros are fine.
1.27a sends the same version byte as 1.27b. Both send 0x1B in SID_AUTH_INFO, so a server can't tell them apart at that point. They differ in the EXE version in SID_AUTH_CHECK. ⚠️ From another project's server log; not yet tested with a 1.27a client here.
If the client disconnects right after logging on ("connection to Battle.net has been lost"), check that the SID_AUTH_ACCOUNTLOGONPROOF reply is exactly 24 bytes.
Sources and credits
- Command Center: WARCRAFT3-FIELD-NOTES.md: observed from a real Warcraft III: The Frozen Throne 1.27b client on September 11, 2026
- wc3-classic-revival, by ValeenMar: a PvPGN server log of a 1.27a client's
SID_AUTH_INFO, showing version byte0x1B - BNETDocs, Battle.net Chat Server Protocol Overview: written by Kyro, and edited 11 times since.
- BNETDocs, NLS/SRP Protocol: written by Sixen, and edited 11 times since.
This page is written in our own words. BNETDocs is credited for its research; none of its text is copied. See Credits.