Valhalla Legends Forums Archive | Battle.net Bot Development | Can someone confirm this?

AuthorMessageTime
DeCloak
Hello, I'm very new to making bots and I want to make sure I'm getting started in the right place.
I spent yesterday reading threads and posts in this forum and just want to confirm what I have found out and make sure I'm going in the right direction. Anyways, (correct me if I'm wrong) but a bot receives packets, interprets them and then sends a response. I have already downloaded Ethereal and have run it while connecting to battle.net... I do not understand how to tell what the packet is saying however.
This is probably because Bnetdocs was offline yesterday though and I hope to learn more about that. I'm a newcomer to VB6 and want to use that to make the bot(very simple bot, just needs to connect for learning puprposes). Ok how do i tell which packets is which?

Example Packet I recieved:
0000  00 30 bd b8 0d e3 00 08  a1 14 fa cb 08 00 45 00   .0...... ......E.
0010  00 30 5b 6f 40 00 80 06  49 85 c0 a8 02 32 3f f1   .0[o@... I....2?.
0020  53 08 04 11 17 e0 67 65  4d 7c 00 00 00 00 70 02   S.....ge M|....p.
0030  ff ff 5c 79 00 00 02 04  05 b4 01 01 04 02         ..\y.... ...... 

This packet has no data? (i think) and i think its the BW client telling battle.net its still there... is this at all correct? I'll post a followup later on this thread with more stuff I'm not possitive on. I do google before posting dont flame the noob please =) Thanks!
Edit: fixed it so it made sense. =]
March 12, 2007, 10:58 PM
iNsaNe
Look for places that begin with "FF". If you see "FF 50" that means you are sending 0x50, which is SID_AUTH_INFO. That is just an example. Another example would be "FF 25", which is 0x25, which is SID_AUTH_PING.

"FF" is the header of the data. The next number (in hex) is the ID of the packet, stated above.
March 12, 2007, 11:12 PM
UserLoser
[quote author=iNsaNe link=topic=16476.msg166660#msg166660 date=1173741142]
Look for places that begin with "FF". If you see "FF 50" that means you are sending 0x50, which is SID_AUTH_INFO. That is just an example. Another example would be "FF 25", which is 0x25, which is SID_AUTH_PING.

"FF" is the header of the data. The next number (in hex) is the ID of the packet, stated above.
[/quote]

SID_PING*.

Threadstarter: the log dump you posted isnt relevant to bot development
March 12, 2007, 11:19 PM
DeCloak
Ok, BnetDocs is still down so I can't see what I'd need to do to begin this simple bot program. I'm also having trouble using any bot source code because I only have Visual Basic 2005 Express edition and it wont upgrade old code. (like foolops src and greetbot src which i grabbed off this forum) So i guess I'm starting from scrath...

Does anyone have a source code compatible with VB 2005 Express I could have? Is there a program that helps interpret packets Ethereal catches? If so please provide a link.

Thanks for your quick replies & best regards, DeCloak.
March 12, 2007, 11:34 PM
MyStiCaL
GreetBot is a C++ developed bot,
FooLOps Is a Visual Basic 6 developed bot,

Learn the programming language by tutorials, and books before asking to use a source when you don't even know what language they are in or what language you are using besides reading the title of your window, Programming is NOT hexing.
Your on a whole new level now bud.
March 13, 2007, 12:06 AM
l2k-Shadow
btw, when packet logging, weed out all the packets that have a length of 0 as you don't need to examine those, ex filter: tcp.port==6112 && tcp.len>0
March 13, 2007, 1:29 AM
DeCloak
Shadow: Thanks for the advice, ill add that to the filter.

Theres a thread in this forum for newbies, I have read this many time over. I'm trying to do what it says but without BnetDocs I can't do much figuring out what the packets mean. Anyone have any idea when this will be back up?
March 13, 2007, 3:52 AM
MysT_DooM
prety much everything on bnetdocs has been discussed on these forums so you can use the search button to look up certain packets and im sure you'll find formats for them or maybe, if lucky some code!
March 13, 2007, 4:09 AM

Search