[Rustyclippers]

Which timings do you increase or all of them? How much do you usually increase it?

It depends what your doing in the background, forground, and your hardware. I use 3 different preset scripts, a fast medium and slow script.

IF you want no errors, you'll be running a fairly inefficient script. It will have to take into account a slow chocobo, slow loads from other players ect. As for wich timings to increase, mostly just the time spent in race. If you have a slow system you can put 1500 delays between numpad 0's (i only do that with 9 ffxiv's open).

Sending commands to the program ID allows you to run multiple instances of the game without script errors. i think the script provided will hop between active windows, using the below method will not.

Code:

^s::
WinGet, programid, List, FINAL FANTASY
Loop
    {
    Sleep 750
    ControlSend,,{Numpad0}, ahk_id %programid1%

---

Below is a script I use, to give you guys some ideas.

THIS WILL NOT WORK WITHOUT TINKERING

I use scrubby pixel reading because I cant actually program worth a damn.

The pixel search is looking for "red" in the chat box (you need to set your own coords with Autoit window spy). IF all races are full, run the queue loop again (if any red message is in your chat box it will also do this).

The pixelgetcolor is searching for the white background of the race resuls screen. It will leave 5-10 seconds after the race is over.

Both pixel search and pixel get colour only work in the active window. you cannot minimize this script. Also note the lack of W being pressed. you will not run around saucer

Code:

/::
WinGet, programid, List, FINAL FANTASY

loop
{
Queue:
    loop
    {
    sleep 1000
    ControlSend,,{Numpad0}, ahk_id %programid1%
    Sleep 1000
    ControlSend,,{Numpad0}, ahk_id %programid1%
    Sleep 1000
    ControlSend,,{Numpad0}, ahk_id %programid1%
    Sleep 1000
    ControlSend,,{Numpad0}, ahk_id %programid1%
    Sleep 1000
    ControlSend,,{Numpad0}, ahk_id %programid1%
    Sleep 1000
    ControlSend,,{Numpad0}, ahk_id %programid1%
    Sleep 1000
    ControlSend,,{Numpad0}, ahk_id %programid1%
    Sleep 1000
    PixelSearch, px, py, 28, 550, 207, 623, 0x4747EE, 3, Fast
    If ErrorLevel
        {
            Sleep 37000
            ControlSend,,{Numpad0}, ahk_id %programid1%
            Sleep 1000
            break
        }
    Else
        Goto, Queue
    }
    loop
    {    
        sleep 2000
        PixelGetColor, color, 571, 359
        if color = 0xd6dfe6
            {
                Sleep 10000
                ControlSend,,{Numpad0}, ahk_id %programid1%
                Sleep 500
                ControlSend,,{Numpad0}, ahk_id %programid1%
                Sleep 10000
                break
            }
        else    
            {
                Sleep 1000
                continue
            }
    }
}

---

I use this script in conjunction with the script i posted above. It looks for the color on the letter M in stamina and sprints until it doesnt read that anymore.

Code:

^x::
WinGet, programid, List, FINAL FANTASY
loop
{
    Sleep 1000
    PixelGetColor, color, 285, 523
    while color = 0x39b6de
    {
        ControlSend,,{W down}, ahk_id %programid1%
        PixelGetColor, color, 285, 523
    }
    Sleep 1000
    if color != 0x39b6de
    {
        ControlSend,,{W up}, ahk_id %programid1%
    }
}

Remember you will have to use your own coords for pixel functions, my ui is different then yours. Do not use this without opening up AutoIT window spy and editing the coords.

(I have my ffxiv in windowed mode, in the smallest window possible. Race results screen is dragged to the very bottom left)

I Just posted these to give people a couple ideas, the script could easily be improved upon.