fataly Posted March 13, 2009 Posted March 13, 2009 Old:http://www.youtube.com/watch?v=JoxKzvphXPANew:memory reading, inventory check / itemreaderAutoHealing, Merc checker.and my visual basic 6 project, full tcp packet support. (Private) http://img15.imageshack.us/img15/5297/26033551ts0.jpgIdea of this topic is get info about diablo 2 memory offsets, so if u got these ( im lazy to search ) post here Example: Last chat msg --> 0x6FBCB830
Developers Jos Posted March 13, 2009 Developers Posted March 13, 2009 What is the AutoIt3 example you are sharing here? SciTE4AutoIt3 Full installer Download page - Beta files Read before posting How to post scriptsource Forum etiquette Forum Rules Live for the present, Dream of the future, Learn from the past.
fataly Posted March 14, 2009 Author Posted March 14, 2009 Not yet nothing, im working with bot atm. I post example on here when it can be tested in public.
jvanegmond Posted March 14, 2009 Posted March 14, 2009 Hey fataly, just a suggestion. Maybe it would be better to go to the forums that are specifically for Diablo II bots. You will get a better response there. As for the rest, maybe wait until Blizzard comes out with the new Diablo II update and then write the bot. Because I doubt it's not going to break as much as possible existing bots. github.com/jvanegmond
E1M1 Posted March 14, 2009 Posted March 14, 2009 Sorry if my reply dont like u, but I just write what I know. I tell you 1 thing, IF your bot is written in autoit, it will be only good example, but it ( sorry for bad word but) sucks in public games.Awesom-o bot is good enugh to beat all autoit diablo 2 bots. it's just the truth.Reason:1)autoit is slower 2)autoit uses mostly pixelsearch 3)no multi treating in autoit. edited
Skrip Posted March 15, 2009 Posted March 15, 2009 (edited) it's just the truth.Reason:1)autoit is slower 2)autoit uses mostly pixelsearch 3)no multi treating in autoit.Your reasons are shitty. You can make a perfectly fine bot in AutoIt, when you know what you are doing.Reason 1: Why does it need to be faster? Perhaps a faster Pixelsearch() but other than that, it would probably be fine.Reason 2: There's other ways to do things. Pixel search still works fine.Reason 3: I'm not sure what 'multi treating' is. But I'm going to guess that you meant 'multi threading'; why does that matter? What are you going to to in your other threads? Edited March 15, 2009 by Firestorm [left][sub]We're trapped in the belly of this horrible machine.[/sub][sup]And the machine is bleeding to death...[/sup][sup][/sup][/left]
ChangMinYang Posted March 15, 2009 Posted March 15, 2009 it's just the truth.Reason:1)autoit is slower 2)autoit uses mostly pixelsearch 3)no multi treating in autoit. Is it truth? ha ha ha ha ~ Truth based on your 'think-able, knowledge, programming-skill'. [2009-03-15(Sun) 11:29:12.234] [L_9881] ycmMemSearch[0x0FC00000 , 0x0FBE0000 , 0x0004 , 0x000E0000 , 0x001000 , 0x0004 , 0x00020000] ACCEPT[0x0000000000000000] Value '47010000C20100000000000000000000' in 0s051 [2009-03-15(Sun) 11:29:12.296] [L_9881] ycmMemSearch[0x0FD40000 , 0x0FD40000 , 0x0004 , 0x00156000 , 0x001000 , 0x0004 , 0x00020000] ACCEPT[0x000087180000B30F] Value '47010000C20100000000000000000000' in 0s107 [2009-03-15(Sun) 11:29:12.375] [L_9881] ycmMemSearch[0x0FEA0000 , 0x0FEA0000 , 0x0004 , 0x00100000 , 0x001000 , 0x0004 , 0x00020000] ACCEPT[0x0000000000000000] Value '47010000C20100000000000000000000' in 0s188 [2009-03-15(Sun) 11:29:12.609] [L_9881] ycmMemSearch[0x105E7000 , 0x10000000 , 0x0080 , 0x0003D000 , 0x001000 , 0x0004 , 0x01000000] ACCEPT[0x0000000000000000] Value '47010000C20100000000000000000000' in 0s427 [2009-03-15(Sun) 11:29:12.656] [L_9881] ycmMemSearch[0x10690000 , 0x10690000 , 0x0004 , 0x01000000 , 0x001000 , 0x0004 , 0x00020000] ACCEPT[0x0800000000010005] Value '47010000C20100000000000000000000' in 0s469 [2009-03-15(Sun) 11:29:13.593] [L_9881] ycmMemSearch[0x11690000 , 0x11690000 , 0x0004 , 0x01000000 , 0x001000 , 0x0004 , 0x00020000] ACCEPT[0x0800000000010005] Value '47010000C20100000000000000000000' in 1s413 [2009-03-15(Sun) 11:29:14.562] [L_9881] ycmMemSearch[0x12690000 , 0x12690000 , 0x0004 , 0x02000000 , 0x001000 , 0x0004 , 0x00020000] ACCEPT[0x0800000000010006] Value '47010000C20100000000000000000000' in 2s381 [2009-03-15(Sun) 11:29:15.984] [L_9881] ycmMemSearch( 252 , 0x0FC00000 , 0x00010000 , 0x017FFFFC , 0x00000000 , False , Int[00000147] , Int[000001C2] , Int[ 0] , Int[ 0] ) Search[0x00010000~0x14010000][320MB] AppMem[0x00010000~0x7FFEFFFF][001GB] Found[1] in 3s801
LithiumLi Posted March 15, 2009 Posted March 15, 2009 (edited) why does that matter? What are you going to to in your other threads?Pickit + PotBot/Chicken + Kill all are running roughly at same time so more threads the better, but Autoit is still possible to make a good Diablo bot but don't go playing hardcore with a Autoit bot Edited March 15, 2009 by LithiumLi
Developers Jos Posted March 15, 2009 Developers Posted March 15, 2009 Idea of this topic is get info about diablo 2 memory offsets, so if u got these ( im lazy to search ) post here Not yet nothing, im working with bot atm. I post example on here when it can be tested in public.Closing thread as this clearly has nothing to do with sharing an example.Please use the forums for the intended purpose only.Jos SciTE4AutoIt3 Full installer Download page - Beta files Read before posting How to post scriptsource Forum etiquette Forum Rules Live for the present, Dream of the future, Learn from the past.
Recommended Posts