A multi-point auto clicker repeats clicks across several screen coordinates. It is useful when a task moves through a stable set of controls: click the first button, choose a second option, confirm, and return to the start.

The key word is stable. A coordinate-based sequence does not understand what is on the screen. If a window moves or a dialog appears, the same point can activate something else.

When multi-point clicking is the right tool

Use a point sequence when:

  • Every target remains in a predictable position.
  • The workflow uses mostly one mouse button.
  • Each cycle follows the same order.
  • The target responds at a consistent speed.
  • You can supervise the first runs.

Use a macro recorder instead when the task includes text entry, keyboard shortcuts, mouse movement that matters, mixed buttons, or different pauses between steps. The auto clicker versus macro recorder guide explains the distinction.

Prepare the screen first

Before capturing a point:

  1. Open the target app and close unrelated windows.
  2. Put the window in its final position and size.
  3. Finish any zoom or display-scaling changes.
  4. Move destructive actions such as Delete, Send, Buy, or Confirm away from the planned path when possible.
  5. Create disposable test data.

If the workflow spans two monitors, read the multi-monitor setup guide before saving coordinates.

Add points in workflow order

Open AT Auto Clicker, enable Points, and capture the center of the first target. Add each later target in the exact order it should receive a click.

Aim for the middle of a control rather than an edge. Borders can shift with window size, responsive layout, or hover state. A large stable target is more reliable than a small icon.

Write the intended sequence in plain language before testing:

  1. Open the item.
  2. Choose the option.
  3. Confirm the change.
  4. Return to the starting screen.

Compare the saved point list with that plan.

Run one slow cycle

Set a 1000 ms interval and run one complete cycle. Keep your hand near the stop hotkey and watch every click.

Check:

  • Did each point land inside the intended target?
  • Did the screen finish updating before the next point?
  • Did a menu or tooltip cover the following target?
  • Did the final click restore the same starting state?
  • Can the cycle repeat without drifting?

If the last step does not return to a predictable state, the workflow is not a safe loop yet.

Tune the timing

After three correct slow cycles, reduce the interval to 750 ms or 500 ms. Retest after each change.

If only one transition is slow, a global timer may waste time on every other point. A recorded script can preserve a longer pause at that transition while keeping other steps faster.

Do not solve a timing problem by adding duplicate points. That can create two actions when the app responds normally.

Choose a stopping rule

For early tests, use a fixed number of cycles. Five cycles are enough to reveal many timing and coordinate problems.

Use a duration only when the sequence ends in the same safe state each time. Avoid continuous mode until:

  • The stop hotkey has been tested.
  • The window cannot move unexpectedly.
  • Notifications and pop-ups are controlled.
  • The automated path contains no irreversible action.
  • A person will notice if the screen changes.

Save a known-good version

Name the configuration after the task and layout, such as “test-form-100-percent-scale-v1.” A useful name records what must remain stable.

Do not overwrite the known-good version while experimenting with faster timing. Save a second version so you can return to the reliable setup immediately.

Common multi-point failures

Every point is offset

Display scaling, resolution, or monitor layout probably changed. Restore the original setup or capture all points again.

The first cycle works but later cycles fail

The workflow is not returning to the same state, or one step needs more time. Slow the sequence and inspect the transition where it diverges.

A context menu changes the target

Right click can open a menu over the original coordinate. Use a complete recorded sequence or add a deliberate next point for the menu item after confirming the layout is stable.

A dialog appears occasionally

Intermittent dialogs make unattended coordinate automation unsafe. Handle the condition manually or use supported automation that can identify interface elements.

Frequently asked questions

Can every point use a different mouse button?

A simple timer is best for one repeated button. Use a recorded script when a workflow mixes left, right, middle, and keyboard input.

How many points should I add?

Use only the points required for one repeatable cycle. More points increase the number of assumptions that must stay true.

Can I use points across two monitors?

Yes, but coordinate changes are more likely when displays reconnect, reorder, or use different scaling. Test after every display change.

Bottom line

A reliable multi-point sequence begins with a stable screen, a written order, one slow cycle, and a fixed stop. Speed comes last.