Warcraft II

[raylu]

Code Select Expand

FF 50 28 00 00 00 00 00 EC AF A6 0B 73 AC 88 00 00 20 58 7D 99 CB C6 01 76 65 72 2D 49 58 38 36 2D 30 2E 6D 70 71 00 00

Code Select Expand

.P(.........s.... X}....ver-IX86-0.mpq.....

Either I'm doing something very very wrong, my packetlogger got seriously screwed up, or B.net just changed their protocol for WC2 again...

[Kayla]

Hmm my connection on Warcraft 2 was interupted about 6 times in less than 13 minutes.  None of my other warcraft 2 logins were affected.  It was really weird though.

[l2k-Shadow]

check your verbyte

[Barabajagal]

War2 doesn't use SID_AUTH packets... A correct emulation would look something like this:

[10:59:32 PM] SEND SID_CLIENTID2
[10:59:32 PM] SEND SID_LOCALEINFO
[10:59:32 PM] SEND SID_STARTVERSIONING
[10:59:34 PM] RECV SID_CLIENTID
[10:59:34 PM] RECV SID_LOGONCHALLENGEEX
[10:59:34 PM] RECV SID_PING
[10:59:34 PM] SEND SID_PING
[10:59:34 PM] RECV SID_STARTVERSIONING
[10:59:35 PM] SEND SID_REPORTVERSION
[10:59:37 PM] RECV SID_REPORTVERSION
[11:00:43 PM] SEND SID_CDKEY2
[11:00:44 PM] RECV SID_CDKEY2
[11:00:44 PM] SEND SID_UDPPINGRESPONSE
[11:00:44 PM] SEND SID_LOGONRESPONSE
[11:00:46 PM] RECV SID_LOGONRESPONSE

It's usually best to be on the safe side if possible, which in this case means emulating the way the actual game logs in correctly.

Edit: when ver-ix86-0 is given for lockdown clients, it means something is out of date (usually verbyte like shadow said).

[Denial]

Yesterday alot of bots were being disconnected that were on warcraft II for a period of 10 minutes to an hour around 6-8pm pacific time yesterday i heard a lot of complaints from it. I myself was not effected in the slightest bit.

[raylu]

Oops...sent the SC verbyte...heh...

[brew]

War2 doesn't use SID_AUTH packets... A correct emulation would look something like this:

[10:59:32 PM] SEND SID_CLIENTID2
[10:59:32 PM] SEND SID_LOCALEINFO
[10:59:32 PM] SEND SID_STARTVERSIONING
[10:59:34 PM] RECV SID_CLIENTID
[10:59:34 PM] RECV SID_LOGONCHALLENGEEX
[10:59:34 PM] RECV SID_PING
[10:59:34 PM] SEND SID_PING
[10:59:34 PM] RECV SID_STARTVERSIONING
[10:59:35 PM] SEND SID_REPORTVERSION
[10:59:37 PM] RECV SID_REPORTVERSION
[11:00:43 PM] SEND SID_CDKEY2
[11:00:44 PM] RECV SID_CDKEY2
[11:00:44 PM] SEND SID_UDPPINGRESPONSE
[11:00:44 PM] SEND SID_LOGONRESPONSE
[11:00:46 PM] RECV SID_LOGONRESPONSE

It's usually best to be on the safe side if possible, which in this case means emulating the way the actual game logs in correctly.

Edit: when ver-ix86-0 is given for lockdown clients, it means something is out of date (usually verbyte like shadow said).

Who cares about being on the safe side. Just go with the X-SHA logon sequence (like many other people do)
It saves time/room for error and is just easier to implement rather then adding support for the legacy sequence.
@Denial Yeah.. for some reason my ops (WAR3) and my main chat bot (W2BN) were randomly disconnecting yesterday. I think the server is just taking a shit.

[iago]

Who cares about being on the safe side. Just go with the X-SHA logon sequence (like many other people do)
It saves time/room for error and is just easier to implement rather then adding support for the legacy sequence.
@Denial Yeah.. for some reason my ops (WAR3) and my main chat bot (W2BN) were randomly disconnecting yesterday. I think the server is just taking a shit.

Could it have anything to do with using the wrong login sequence? Because if it does, then that overall post is pretty funny.

[l2k-Shadow]

Could it have anything to do with using the wrong login sequence? Because if it does, then that overall post is pretty funny.

Oops...sent the SC verbyte...heh...

[raylu]

I think he's saying that brew was getting disconnected for using the wrong logon sequence.

[iago]

I think he's saying that brew was getting disconnected for using the wrong logon sequence.

Yeah, you'll note that I didn't quote the OP, I quoted Brew.

[Spht]

It's usually best to be on the safe side if possible, which in this case means emulating the way the actual game logs in correctly.

Right.  I figured everyone would've learned their lesson from Japan Starcraft--at first Battle.net accepted the traditional Starcraft logon method for SCJ, even though the actual client uses the legacy messages.  But now you will be banned for trying it

[Hdx]

There is only one problem with people emulating the OOLS.
BNLS dosen't support CDKey encoding for OOLS.
Which is why I've been pushing Skywing to add an additional flag onto the cdkey packs that would not add the 0 dword into the equation. (Which is the only diffrence)
So anyone who uses BNLS for the cdkey is forced into useing SID_AUTH.
~Hdx