Saved click points are screen coordinates, not named buttons. When the screen layout changes, the coordinate remains the same while the intended target moves.
Use this checklist when every click is offset, one point is wrong, or a saved sequence worked yesterday but fails today.
1. Stop and run one harmless point
Do not keep replaying the full sequence. Create one point in the center of a disposable test target, use a 1000 ms interval, and run one click.
If the new point works, the old coordinates are stale. If the new point is also offset, focus on display, remote-session, or pointer issues.
2. Put the window in its final position
Move and resize the target before capturing points. If it was maximized during setup, maximize it again. If it was windowed, restore the same size and location.
A few pixels may not matter for a large button, but a small icon or menu item can move outside the saved point.
3. Check Windows display scaling
Windows can scale text and controls to 125%, 150%, or another value. A scaling change can affect how apps map visual positions to screen coordinates.
Open Display settings and check Scale for every monitor. Restore the layout used when the points were created, or keep the current layout and capture all points again.
Sign out or restart an app if Windows requests it after a scaling change.
4. Check resolution and monitor order
A changed resolution alters the coordinate space. Connecting, disconnecting, or reordering displays can also move the virtual desktop origin.
In Display settings, arrange monitors to match their physical positions. Then open the target and recapture points. See the multi-monitor auto clicker guide for a stable setup process.
5. Reset browser or app zoom
Browser zoom can move a web control without changing the window itself. Reset to the expected level, often 100%, and reload the page.
Desktop apps may have their own canvas zoom, sidebar width, or compact layout. Save those conditions with the script.
6. Aim for the target center
An edge coordinate is vulnerable to small layout changes and hover effects. Capture the middle of the clickable area, away from scrollbars, borders, and adjacent destructive controls.
If a target is too small, slow down and supervise rather than compensating with multiple nearby points.
7. Close overlays and notifications
Tooltips, menus, notifications, chat windows, and modal dialogs can cover the correct coordinate. Move the pointer away and wait for hover content to disappear before capturing a point.
A sequence that can trigger an unpredictable modal is not safe for unattended coordinate automation.
8. Consider remote desktop behavior
Remote sessions can use a different resolution and scaling from the physical PC. Reconnecting may resize the session. Capture points inside the same session configuration that will run them.
Do not assume a script recorded locally will match a remote screen.
Diagnose the pattern
| Symptom | Likely cause |
|---|---|
| Every point offset equally | Resolution, scaling, or monitor layout |
| One point wrong | Target moved or point captured at an edge |
| First cycle works, next fails | Screen does not return to the same state |
| Works at 100% zoom only | Browser or app zoom |
| Fails after reconnecting monitor | Virtual desktop coordinates changed |
| Correct point but no action | Wrong mouse button, focus, or permissions |
If the point is correct but the target ignores input, use the general Windows troubleshooting checklist.
Rebuild rather than patch a broken point list
After a display change, recapture every point in order. Moving only one point can hide a consistent offset and leave later failures.
Run one slow cycle, then three cycles, before restoring the original repeat count.
Frequently asked questions
Why is the pointer correct but the click lands elsewhere?
Remote sessions, scaling, or app-specific coordinate mapping can create an apparent mismatch. Test a fresh point on the primary monitor at 100% zoom.
Can I make points independent of screen position?
A coordinate clicker cannot identify a control by text or role. Use supported element-aware automation when the layout changes frequently.
Should I use current-cursor mode instead?
It can help for a short supervised task because you aim manually. It is not a fix for a long multi-point sequence.
Bottom line
Wrong-location problems are usually layout problems. Stabilize the window, scaling, resolution, zoom, and monitor order; then capture a clean point list from scratch.
