S>C 0x3A SID_LOGONRESPONSE2

Transport Layer:	Transmission Control Protocol (TCP)
Application Layer:	Battle.net v1 TCP Messages (SID)
Message Id:	`0x3A`
Message Name:	`SID_LOGONRESPONSE2`
Direction:	Server to Client
Used By:	Starcraft Original, Starcraft Broodwar Diablo II, Diablo II Lord of Destruction
Message Format: ^{(does not include protocol header)}	`(UINT32) Status (STRING) Additional information (optional)`

Remarks

Contains the response to the XSHA-1 logon request from C>S 0x3A SID_LOGONRESPONSE2.

Status	Description
`0x00`	Success
`0x01`	Account does not exist
`0x02`	Incorrect password
`0x03` (Diablo II ONLY)	That account is corrupted. Please report this to [email protected] immediately.
`0x06`	Account closed, see additional information

The additional information is absent, including the null-terminator, unless the status is 0x06.

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.

Diablo II: You were disconnected from Battle.net. Please reconnect.

StarCraft: You could not be logged on to the server with that account. Please try again later.

Sunday, February 26, 2012 | Edited: Thursday, December 3, 2020

Kyro

Comments

Accused
Wed Dec 5, 2007 12:19am UTC

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.

EDIT:

Confirmed.

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).......

Kyro
Wed Dec 5, 2007 9:19am UTC

Updated. Thanks for the contribution.

Leaky
Wed Dec 5, 2007 5:10pm UTC

0x06 has been account closed forever...

Accused
Wed Dec 5, 2007 6:19pm UTC

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.

Leaky
Wed Dec 5, 2007 6:56pm UTC

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...

Accused
Wed Dec 5, 2007 7:27pm UTC

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

Leaky
Wed Dec 5, 2007 9:32pm UTC

:P thx for telling us we forgot it tho

Caaaaarrrrlll
Fri Dec 27, 2019 2:21am UTC

Updated format and remarks for clarification and readability.

timfelgentreff
Tue Aug 11, 2020 5:29am UTC

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