StarCraft Shareware and StarCraft Japanese: logon to chat

SSHRJSTR

The oldest logon, used by StarCraft Shareware and StarCraft Japanese. Both now require an update to a newer StarCraft.

#ClientServerWhat happensConfidence
1 0x01 → Protocol byte: BNCS follows. ✅ Verified
2 SID_CLIENTID → ⚠️ Single source
3 SID_LOCALEINFO → ⚠️ Single source
4 SID_SYSTEMINFO → ⚠️ Single source
5 SID_STARTVERSIONING → Names the game (SSHR or JSTR) and version byte. ⚠️ Single source
6 ← SID_CLIENTID ✅ Verified
7 ← SID_LOGONCHALLENGE Server token only, with no UDP code. ⚠️ Single source
8 ← SID_PING ✅ Verified
9 SID_PING → ⚠️ Single source
10 ← SID_STARTVERSIONING ⚠️ Single source
11 SID_REPORTVERSION → ⚠️ Single source
12 ← SID_REPORTVERSION 0x02 when the version passes. ⚠️ Single source
StarCraft Japanese only
13 SID_CDKEY → Plain-text CD key. ⚠️ Single source
14 ← SID_CDKEY 0x01 accepted. ⚠️ Single source
Logging on
15 SID_LOGONRESPONSE → ⚠️ Single source
16 ← SID_LOGONRESPONSE 0x01 logged on. ⚠️ Single source
17 SID_UDPPINGRESPONSE → ⚠️ Single source
Entering chat
18 SID_ENTERCHAT → ⚠️ Single source
19 SID_GETCHANNELLIST → ⚠️ Single source
20 SID_JOINCHANNEL → ⚠️ Single source
21 ← SID_ENTERCHAT ⚠️ Single source
22 ← SID_GETCHANNELLIST ⚠️ Single source
23 ← SID_CHATEVENT ⚠️ Single source

Remarks

Defunct on official servers. Both games now show a required update to the free StarCraft 1.18, which no longer uses this logon.

Which logon challenge. BNETDocs recorded these clients receiving SID_LOGONCHALLENGE. The Atlas server sends SID_LOGONCHALLENGEEX in reply to SID_CLIENTID instead. A capture from a real client would settle which one they expect.

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 John Leighow.
Edit on GitHub | Page history