However, this is generally not needed for the SendInput/Play modes because they automatically postpone the user's physical mouse activity until afterward. The BlockInput command can be used to prevent any physical mouse activity by the user from disrupting the simulated mouse events produced by the mouse commands. The speed parameter or SetDefaultMouseSpeed can be used to reduce the speed (in the default SendEvent mode only). In addition, some applications and games may have trouble tracking the mouse if it moves too quickly. The SendPlay mode is able to successfully generate mouse events in a broader variety of games than the other modes. This command uses the sending method set by SendMode. In other words, the cursor will be moved from its current position by X pixels to the right (left if negative) and Y pixels down (up if negative). R: The X and Y coordinates will be treated as offsets from the current mouse position. If blank or omitted, the X and Y coordinates will be used for absolute positioning. To visually move the mouse more slowly - such as a script that performs a demonstration for an audience - use SendEvent or SendMode Event (optionally in conjuction with BlockInput). Speed is ignored for SendInput/Play modes they move the mouse instantaneously (though SetMouseDelay has a mode that applies to SendPlay). A speed of 0 will move the mouse instantly. Otherwise, specify the speed to move the mouse in the range 0 (fastest) to 100 (slowest), which can be an expression. If blank or omitted, the default speed (as set by SetDefaultMouseSpeed or 2 otherwise) will be used. Coordinates are relative to the active window unless CoordMode was used to change that. The X and Y coordinates to move the mouse to, which can be expressions. MouseMove, X, Y, Speed, Relative Parameters X, Y MouseMove - Syntax & Usage | AutoHotkey MouseMove

Autohotkey auto typer script delay