Help me transform AHK in AUTOIT

[gersonjosue]

I overlooked in AHK just what PixelSearch is and the command that it processes, however I don't get my they have a string Fast|RGB in there if they don't use it. The 38 is is a number you tell the command pixelsearch to use as a shader, it will be divided in half and -/+ to the color. It cannot go below 0 and above 255.

PixelSearch ( left, top, right, bottom, color [, shade-variation [, step [, hwnd]]] )

I thought it was a step at first being the Fast parameter, Fast being a macro for 2 or more but it isn't.

friend, try this Sunday the entire script, it is working right, the trigger all the keys right, my problem is in the "pixelsearch" more I try I get it fuses in variations of color you find the closest color, do you think changes q the color from program to program? example: I use a tool of autohotkey to get the colors and details, is the "spy Autoit3 windows" with everything he can get more with the tool of Autoit "Autoit info windows" can not read anything on the screen, you think is difference between the colors from one program to another? or not has nothing to do.

[gersonjosue]

I know I'm a boring guy with so many questions, have patience with me, yet will stay good in Autoit, you think the script has many features that it is heavier? in my script in AHK, he is sending the commands and fast, I realized that some of the autoit it breaks, do not know if you have something to do with time, plus you have an idea, have hours that can not control the character because it seems the keys sent by autoit, it fuses the keyboard I do not know what it could be, perhaps autoit is a good compatibility with Windows Vista?, I try to see in Windows XP.

[TerarinK]

If TimerDiff($iHP) > 110 Then _HP()
                If TimerDiff($iMP) > 100 Then _MP()
                If TimerDiff($iHPPet) > 100 Then _HPPet()
                If TimerDiff($iNumberToPick) > 180 Then _NumberToPick()
                If TimerDiff($iTimeToGet) > 130 Then _TimeToGet()
                If TimerDiff($iTargetFind) > 1000 Then _TargetFind()

The 110,100,100,180,130 and the 1000 are all times in mm. So 1000 would be the command for exeuting every second. You know what I would do, I would setup the HP, MP and possible to setup the HPPet to scroll on a AdlibEnable function since your checking them 1/10 per second. One more thing why not have a clock because the game must run on a clock that ticks every 250 mm possible 100 mm but most likely not. A easy enough way to tell the ticks in a game is to kill two beast and see how different the beast appear back, if they appear the same then you have some system of ticks. However you could see a system that seems impossible by incorporating the thing into a bucket and as each bucket appears puts the mobile on. These systems run alot more effectively and can do whole areas in a single function (sorry talking about the code base).

However as I see it the lowest amount of time is .1 second or 100 and that is simply targeting and getting stuff totally seperate from the games actually functions so you can incorporate them into a single function that says your in a State of killing and till the thing your killing is dead then return you back to normal those getting all the eq and then repeat.

[gersonjosue]

If TimerDiff($iHP) > 110 Then _HP()
                If TimerDiff($iMP) > 100 Then _MP()
                If TimerDiff($iHPPet) > 100 Then _HPPet()
                If TimerDiff($iNumberToPick) > 180 Then _NumberToPick()
                If TimerDiff($iTimeToGet) > 130 Then _TimeToGet()
                If TimerDiff($iTargetFind) > 1000 Then _TargetFind()

The 110,100,100,180,130 and the 1000 are all times in mm. So 1000 would be the command for exeuting every second. You know what I would do, I would setup the HP, MP and possible to setup the HPPet to scroll on a AdlibEnable function since your checking them 1/10 per second. One more thing why not have a clock because the game must run on a clock that ticks every 250 mm possible 100 mm but most likely not. A easy enough way to tell the ticks in a game is to kill two beast and see how different the beast appear back, if they appear the same then you have some system of ticks. However you could see a system that seems impossible by incorporating the thing into a bucket and as each bucket appears puts the mobile on. These systems run alot more effectively and can do whole areas in a single function (sorry talking about the code base).

However as I see it the lowest amount of time is .1 second or 100 and that is simply targeting and getting stuff totally seperate from the games actually functions so you can incorporate them into a single function that says your in a State of killing and till the thing your killing is dead then return you back to normal those getting all the eq and then repeat.

in this case a reading of memory in hp and mp it would be better and more efficient?

I can read the values of the memory of hp and mp with cheat engine.