Since You All Know About Ste4lthBot v1.6 And v1.8 I'll Get Straight To The Point...
-v1.6 Loaded Warcraft III Just Fine...
-v1.8 Gave Me The Following Bug:
_____________________________
|CSBOCX |x||
|¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯|
| / \ run time error '9': |
|/ ! \ subscript out of range|
| ¯¯¯ _____ |
| | OK | |
| ¯¯¯¯¯ |
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
-I've Decided To Code A Bot And Im Getting Same Bug, Yet EternalChat Loads Just Fine...
-Could It Be BNLS Dosent Support Warcraft III Logons With Non C Code? (Dumb Question?, EternalChat Is C Code?)
i will never waste 5 min on ascii again...
BNLS supports any login made with the proper packets. In any case, EternalChat is a VB bot, and I would guess your problem could be that the bots are attempting to use an outdated version byte - EC automatically updates it.
Fpa, have you Packetlogged EternalChat and your bot, and looked at the differences? >:(
omg, I love ascii art!
grr
thnx kaine ill try that
-umm now im confused..
-is there anyway to load war3 using vb without "hexing"?
-how would i go about updating version byte in vb ?
*lol*
packet log client, or working war3 bot, look at the position of the old version byte in your bot, look for that position in packet log, take it.
-im still lost...
-i have ethereal from www.ethereal.com i logged my connection with EC
-afterwards i logged my bots connection
-but ummm i still dont see position of packet for version byte
-am i using wrong packet sniffer?
The version byte is not an entire packet - it's a small part (literally a byte) in one specific packet. Look at one of the protocol specs floating around to find out which packet and where - I won't do *all* your work for you. :P
Actually it's a DWORD (treated as a DWORD internally) and may very well be larger than 0xFF. It just never was, so it has been called a "byte".
I suggest you abuse the Battle.net logon server's ability to keep you up-to-date with correct version DWORD(!) so that you won't have to keep updating the program each time a new patch is released. It would also be very annoying if the public used your bot and you'd have to send out a new version each time. With EternalChat, it will always acquire correct version information from BNLS so that I do not have to make any changes when new game version are released.
I get the same error with my cleanslatebot2.ocx
???
You're evidently coding it wrong then...I can state for a fact that CleanSlateBot.ocx itself is still functional if used correctly, so...
no i put csb.cdkey = "************************"
and csb.product = "3RAW"
and all the other crap so i dont think so.
Since I've never used CleanSlateBot in my own code (considering I code in C it'd be rather difficult), I have no idea what that means. However, since OTHER bots using CleanSlateBot are still functional, you must be handling something wrong. If you weren't, *all* CleanSlateBot clients would be having the same problem.
OK. Heres what I have:
Private Sub con_Click()
csb.Accept = 579728
csb.BNLSBotID = "haze"
csb.BNLSBotPassword = "********"
csb.CDKey = "****************"
csb.Password = "******"
csb.Product = "3RAW"
csb.Server = "63.240.202.131"
csb.Username = "Laeurion-"
csb.HomeChannel = "Clan ozxo"
csb.UseWait = False
csb.UseUDP = True
csb.Disconnect
csb.Connect
End Sub
whats wrong with that...
Stealthbot does the same exact thing.
So, I think this is an overall problem.