Author | Message | Time |
---|---|---|
PaiD | ok i was wondering what is the order in making a bot. Like right when you open the vb program what do you do? | February 15, 2003, 9:55 PM |
Noodlez | click file->new project | February 15, 2003, 10:30 PM |
PaiD | ok i should restate the question. On the connectionions what packets do i send? | February 15, 2003, 10:47 PM |
kows | [quote]click file->new project[/quote] lol | February 15, 2003, 10:48 PM |
Noodlez | the first packet you send (assuming your using star/sexp/war3/d2dv/d2xp) would be 0x50 | February 15, 2003, 11:16 PM |
PaiD | k thx i just got a packet sniffer | February 16, 2003, 12:28 AM |
dRAgoN | [quote]the first packet you send (assuming your using star/sexp/war3/d2dv/d2xp) would be 0x50[/quote] 0x01 8p | February 16, 2003, 2:16 AM |
Atom | in your case, it would prolly be chr(3) | February 16, 2003, 2:19 AM |
MesiaH | depends on if hes making binary bot or chat bot if its binarybot, get the socket connected, then send chr(1), then 0x50. if its chatbot, get the socket connected, then send chr(3) & chr(4) (chr(4) is optional), then username & newline & password, newline. | February 16, 2003, 6:54 PM |
Etheran | hey! just go look at bnet docs! ;D | February 17, 2003, 12:05 AM |
DaRk-FeAnOr | Well it matters if you using WinSocket or BNLS. LoL is BNLS easy. | February 17, 2003, 12:08 AM |
Yoni | [quote]Well it matters if you using WinSocket or BNLS. LoL is BNLS easy. [/quote] /me wonders how you would use BNLS without using sockets | February 17, 2003, 4:09 AM |
Noodlez | i think he means it matters if your using winsock.ocx or CSB | February 17, 2003, 4:12 AM |
haZe | whats chr(4)!! | February 17, 2003, 7:12 AM |
tA-Kane | ^D | February 17, 2003, 2:22 PM |
Eibro | '\4' | February 17, 2003, 4:07 PM |
St0rm.iD | ipban perhaps | February 17, 2003, 5:17 PM |
Camel | [quote]0x01 8p[/quote] its not actually packet 0x01, its just a single byte | February 22, 2003, 5:03 PM |
Noodlez | so? its still a packet. just because if doesnt have the bnet packet header doesn't mean it's not a packet. | February 23, 2003, 2:12 AM |
Camel | how did i know you were going to say that... yes, but you wouldnt call it "packet 0x01", because then you would have to call every othe packet "0xFF" or "0xFF 0xwhatever" [edit] me fail english? | February 23, 2003, 11:56 AM |
St0rm.iD | I prefer referring to them as "bnet messages" instead of "packets," because you have no control over the TCP packets when you're using the TCP layer. | February 23, 2003, 12:35 PM |
Yoni | [quote]no control[/quote] Well, technically you have a little control... Even without using raw sockets, you can change some things in the header with setsockopt. | February 23, 2003, 2:56 PM |
Camel | if you're handy enough. you could send() some data, and then quicly hack the memory before it gets sent | February 23, 2003, 3:08 PM |
Yoni | [quote]if you're handy enough. you could send() some data, and then quicly hack the memory before it gets sent[/quote] ehh... No, if you really wanted to do something like that, you'd install some kind of API hook/jmp before calling send, not do it "quickly after"! | February 23, 2003, 3:10 PM |
Skywing | [quote]if you're handy enough. you could send() some data, and then quicly hack the memory before it gets sent[/quote] By the way, at least on NT your data is quickly passed on to kernel mode drivers, such as NDIS.SYS. You'd have a hard time bothering kernel mode memory from user mode. | February 23, 2003, 4:19 PM |
St0rm.iD | Yoni: notice how I said TCP layer ;) | February 25, 2003, 5:11 PM |