Quote:
Originally Posted by VitaminD
]]well it doesnt just happen in one night, it took him a while to do it starting from something simple and growing to somethign bigger with each release of his previous AIOs It get pretty addicting to do this stuff once you get the hang of it
@AFK guy, that would be nice if Strikes source helps you improve your bot heh. Im suprised you use AHK though, I made a little key presser for a couple things using AHK but its pretty limited imo, and I find it more confusing than Autoit which im learning atm
|
AHK is essentially the same language as AUT/AU3 except it has WAAAAAY more functionality. There is a huge debate over AUT versus AHK and which one is better. IMO AHK is better because the syntax is much easier to read and to control.
AHK has many different built in functions that AUT/AU3 doesn't have. Including hotkey binding which is why I chose AHK in the first place.
My bot started out as a simple key presser, but just like anything else I got way to much into it. I ended up breaking down each thing I needed to do into its own function. Took a long time to sit and watch my charcter grind to figure out all the intricate details of what "could go wrong" and to account for everything.
Yea the one biggest thing strikes source showed me was how to do memory injection with AHK. It was so simple it's just I have never done any DLL calls before.
Man this is gonna be a load of fun now that I can inject into the memory!! Look out aeria... :P
EDIT:
Oh yea strike about multi-threading. A thread is "what is currently happening". So in AHK/AUT/AU3 you can only be doing one thing at a time. You can do a thousand things within one second, but they will all happen one after another, not at the same time. This limits your ability to create more dynamic code.
With 2 threads you could have one function running that is checking for variable in another function running on its own thread.
In the example of AFK Guy. I have one function which searches to screen for signs that you have been attacked, this function runs every 50ms. When this function determines you should attack it sets a variable "DoSwing" to 1. Another function runs every 250ms and checks to see what DoSwing is, if its one it sends swings.
These functions cannot happen at the same time, thats why they are set to run on a timer. However if I had the ability to run multi threads the first function would be looping continuasly with no delay. So would the second function.
If you think about it that would mean that one part of the script is ALWAYS looking to see if you are being attacked, and another part is ALWAYS checking to see if it should swing. (you might think these should be the same function but it works better when they are seperated, at least with single threading it is)
So as you can see multiple threads means almost infinite possibilities.