ok i was wondering what is the order in making a bot.
Like right when you open the vb program what do you do?
click file->new project
ok i should restate the question. On the connectionions what packets do i send?
Quoteclick file->new project
lol
the first packet you send (assuming your using star/sexp/war3/d2dv/d2xp) would be 0x50
k thx i just got a packet sniffer
Quotethe first packet you send (assuming your using star/sexp/war3/d2dv/d2xp) would be 0x50
0x01 8p
in your case, it would prolly be chr(3)
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.
hey! just go look at bnet docs! ;D
Well it matters if you using WinSocket or BNLS. LoL is BNLS easy.
QuoteWell it matters if you using WinSocket or BNLS. LoL is BNLS easy.
/me wonders how you would use BNLS without using sockets
i think he means it matters if your using winsock.ocx or CSB
whats chr(4)!!
^D
'\4'
ipban perhaps
Quote0x01 8p
its not actually packet 0x01, its just a single byte
so? its still a packet.
just because if doesnt have the bnet packet header doesn't mean it's not a packet.
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?
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.
Quoteno control
Well, technically you have a little control...
Even without using raw sockets, you can change some things in the header with
setsockopt.
if you're handy enough. you could send() some data, and then quicly hack the memory before it gets sent
Quoteif you're handy enough. you could send() some data, and then quicly hack the memory before it gets sent
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"!
Quoteif you're handy enough. you could send() some data, and then quicly hack the memory before it gets sent
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.
Yoni: notice how I said TCP layer ;)