D2/D2X
------
(DWORD) Number of games
LIST:
(DWORD)
(DWORD)
(WORD)
(WORD) Host's remote port
(DWORD) Host's IP
(DWORD)
(DWORD)
(DWORD)
(DWORD) Elapsed time (in seconds)
(STRING) Game name (null terminated)
(BYTE) 0 (extra null byte for some reason)
^(STRING) Game Comment Which is done by the host when creating (null terminated)^
~dRAgoN
Hmmmmm, thanks for posting an update. Now if there were some info on binding to UDP so that you can physically send the bot into a game instead of just listing the games that are currently running, then that would be quite handy and really helpful :-/
Check out Eth Bot's source. It can join / create games. Only problem is people can't join the games that the bot creates :(
ethbot can join games already made?
I'm afraid I don't know where to get the source Coltz. :'(
http://aodw.hypermart.net/EthBotFull.zip
Thank you very much Coltz ;D
thank etheran ;)
btw I dont even think other bots can join the game ethbot creates. Also I think the start game is a bit messed up. ;D
Yes, it does not work. it says to high of latency to join the game. And starting game always fails.
I think ethbot was designed to make/join games for another patch, and it hasnt been updated since. Also, ethbot can only join games created by another ethbot, or so I believe.
well say u made ethbot have proxy support and had them both go in same game and start. Would it actually work? I dont think start works eather.
I guess if you logged it in through a seprate CD Key (you have to any way to use on bnet) you could, I don't see why you can't. Only thing I can see anyone worrying about is the stablity of the proxy server you connected to =\
Unless ethbot has udp support, game clients or other bots can't truely join it's games through the standard method. When the game says that the latency is too high, it basically means there wasn't a reply to a UDP packet sent to the game host's IP within a certain alloted amount of time
Well there is udp support. I dont know if its good anough to play games on, but u can log on bnet on udp.
The system for logging on battle.net being able to play games is quite useless when it comes to bots, the client tells the server wether it got the udp packets or not. You don't even have to receive the packets, just tell battle.net that you got them
just as your encryption key is in 0x50's recieve there is also the udp key in 0x50 if sent corectly you recieve back some udp packets 3 if i remember. now if you create your game and someone trys to join your game while your udp socket is not connected 'you can figure out your outcome'
~l)ragon