S>C 0x3A SID_LOGONRESPONSE2
|Transport Layer:||Transmission Control Protocol (TCP)|
|Application Layer:||Battle.net v1 TCP Messages (SID)|
|Direction:||Server to Client|
|Used By:||Starcraft Original, Starcraft Broodwar|
Diablo II, Diablo II Lord of Destruction
(does not include protocol header)
Contains the response to the XSHA-1 logon request from C>S 0x3A SID_LOGONRESPONSE2.
||Account does not exist|
||That account is corrupted. Please report this to [email protected] immediately.|
||Account closed, see additional information|
The additional information is absent, including the null-terminator, unless the status is
On unknown status codes, clients will close the connection to Battle.net and display a default error message. If status
0x06 is sent without the
Additional information field, clients will display the default error message.
You were disconnected from Battle.net. Please reconnect.
You could not be logged on to the server with that account. Please try again later.
0x06: Account has been closed
It was in use about a year ago although I cannot confirm it today since I don't have access to a banned account. But I'm sure it's still there.
0000: FF 3A 2A 00 06 00 00 00 59 6F 75 72 20 61 63 63 ÿ:*....Your acc 0010: 6F 75 6E 74 20 68 61 73 20 62 65 65 6E 20 63 6C ount has been cl 0020: 6F 73 65 64 2E 20 28 38 29 00 osed. (8).......
Updated. Thanks for the contribution.
0x06 has been account closed forever...
I'm not so sure about forever. I've had an account that received this in the past and it expired after the 93 day usual.
yea... it's been account closed since they enacted the closed account system....
soo.. i guess not forever but atleast since as long as i can remember getting that message on bnet...
Oh...I thought you meant the account itself gets closed forever. Yeah I knew the message code 0x06 was there 'forever' it just wasn't documented here which is why I brought it up. I confused what you were saying ;p
:P thx for telling us we forgot it tho
Updated format and remarks for clarification and readability.
pvpgn actually sends the status as a short and adds a 0x0 short for "padding". If you read the status as uint32, these are the status code you get when using this against pvpgn
0x000000 Success 0x010000 Account does not exist 0x020000 Incorrect password 0x060000 Account closed, see additional information