C>S 0x0E BNLS_AUTHORIZE
|Transport Layer:||Transmission Control Protocol (TCP)|
|Application Layer:||BNLS Messages (BNLS)|
|Direction:||Client to Server|
|Used By:||Starcraft Original, Starcraft Broodwar|
Starcraft Shareware, Starcraft Japanese
Diablo Retail, Diablo Shareware
Diablo II, Diablo II Lord of Destruction
Warcraft II BNE, Warcraft III Reign of Chaos
Warcraft III The Frozen Throne
(does not include protocol header)
This message logs on to the BNLS server.
Note: The bot ID is not case sensitive, and is limited to 31 characters.
This message was used to let your bot log into the BNLS service. It is no longer required, but it may still be used for backwards compatibility. If you wish to require your bot to login to BNLS to be able to work, you can change your BNLS password and prevent your bot from logging in. Useful for required patches and such.
To get a bot ID and password, ask Yoni or Skywing.
Note: As of June 28, 2004, BNLS IDs were no longer required to log into BNLS; clients could completely bypass using messages BNLS_AUTHORIZE and BNLS_AUTHORIZEPROOF to log on, and BNLS would validate any client that logged in via these methods. On August 14, 2004, BNLS was again changed so that, while clients can still bypass using messages BNLS_AUTHORIZE and BNLS_AUTHORIZEPROOF to log on, clients that do support these messages will be validated against the bot ID database, which allows those users who still own bot IDs to disable old versions by changing the password on the account.
no one has commented yet.