Idea on how to modify a greet bot

[AC_Drkan]

Ok on the greet bots when they connect they send packets
(0x03)c
and (0x04)d

Change them to.....?
0x1
to be a blizzrep?

[Eric]

Ok on the greet bots when they connect they send packets
(0x03)c
and (0x04)d

Change them to.....?
0x1
to be a blizzrep?

... The first packet would be the protocol ID.  Sending 0x03 as the protocol ID would tell the server that you're connecting as a CHAT client and restrict you to public channels, but if you were to change it to 0x01, you'd be telling the server that you're connecting as a binary client which would allow you to enter most of Battle.net's channels, but would also require lots of authentication.

[ChR0NiC]

And I know you didn't mention this, but 0x02 would be FTP.

Edit: In order to become a Blizzard Rep, BNET would have to assign your specific account with a flags of &H1. Which is the same thing they do for GF_PLAYER except they assign the account a flags of &H200000.

[MyndFyre]

And I know you didn't mention this, but 0x02 would be FTP.

Edit: In order to become a Blizzard Rep, BNET would have to assign your specific account with a flags of &H1. Which is the same thing they do for GF_PLAYER except they assign the account a flags of &H200000.

Which means it's pretty much the same thing, only different?  ^_^

[Eli_1]

On a side note, 0x04 tells the server you don't want it to echo back what you send.

[AC_Drkan]

I've tried 0x02 which is a channel ops and it connected but then disconnected in like 10 minutes

Then i tried 0x40 and that was a special guest which was pretty stable and maittained a connection for about 30 minutes.

Pretty cool, i was able to access my op's channel wiht the bot but i accidently had the greet message on my stealth and it sorta flooded it out.

[AC_Drkan]

Ok on the greet bots when they connect they send packets
(0x03)c
and (0x04)d

Change them to.....?
0x1
to be a blizzrep?

... The first packet would be the protocol ID.  Sending 0x03 as the protocol ID would tell the server that you're connecting as a CHAT client and restrict you to public channels, but if you were to change it to 0x01, you'd be telling the server that you're connecting as a binary client which would allow you to enter most of Battle.net's channels, but would also require lots of authentication.

Authenticiation?

What types??

[ChR0NiC]

First of all, try not to post two or more in a row, just use the modify button located in the top right of your current post.

Authenticiation?

What types??

Logon Sequence For 0x50: (Compatible With Every Client, except Chat)

Code Select Expand


SEND ->  Protocol byte (01)
SEND -> SID_AUTH_INFO (0x50)
RECV <- SID_PING (0x25)
RECV <- SID_AUTH_INFO (0x50)
SEND -> SID_PING (0x25) [Optional]
SEND -> SID_AUTH_CHECK (0x51)
RECV <- SID_AUTH_CHECK (0x51)
SEND -> SID_LOGONRESPONSE (0x29)
RECV <- SID_LOGONRESPONSE (0x29)
[Instead of 0x29, you may use 0x3A]
SEND -> SID_LOGONRESPONSE2 (0x3A)
RECV -> SID_LOGONRESPONSE2  (0x3A)
[/0x3A]
SEND -> SID_UDPPINGRESPONSE (0x14) [Game Specific: SEXP/STAR/W2BN]
SEND -> SID_ENTERCHAT (0x0A)


Logon Sequence For 0x1E (Applies to but not limited to D1 and W2)

Code Select Expand


Warcraft 2 BNE (W2BN)
SEND ->  Protocol byte (01)
SEND -> SID_CLIENTID2 (0x1E)
SEND -> SID_LOCALEINFO (0x12)
SEND -> SID_STARTVERSIONING (0x06)
RECV <- SID_LOGONCHALLENGEEX (0x1D)
RECV <- SID_PING (0x25)
RECV <- SID_STARTVERSIONING (0x06)
SEND -> SID_PING (0x25) [Optional]
SEND -> SID_REPORTVERSION (0x07)
RECV <- SID_REPORTVERSION (0x07)
SEND -> SID_UDPPINGRESPONSE (0x14) [Optional]
SEND -> SID_CDKEY2 (0x36)
RECV <- SID_CDKEY2 (0x36)
SEND -> SID_LOGONRESPONSE (0x29)
RECV <- SID_LOGONRESPONSE (0x29)
SEND -> SID_ENTERCHAT (0x0A)


Edit:
Packet structures for each of these packets are available at BNET Docs