Auto Clicker

Auto Clicker clicks for you: the same spot over and over, a few spots in order, or something that shows up on screen — with any mouse button, as a tap or a sustained hold.

The panel opens in Guided setup, which asks one question at a time and ends on a plain-English summary with a Start clicking button. Advanced shows every control at once. The toggle between them is at the top right of the panel, and both edit exactly the same setup — switching never loses an answer.

Guided setup

Answered questions collect as chips across the top; click one to go back to it. Back and Next move between steps, and Next only lights up once the current step has an answer.

What do you want to click?

• The same spot, over and over — idle games, refresh buttons, anything that needs clicking again and again. Then choose Wherever my mouse is (the clicks follow your cursor) or One spot I pick, which opens a full-screen picker: click the spot and ClickTray remembers it.
• A few spots, in order — click A, then B, then C, and repeat. Pick the first spot, then Add another spot for each one after it. Each spot has a then wait time in milliseconds before the next, and can be moved up, moved down or removed. After the last spot it starts again from the first.
• Something that shows up on screen — a button, a pop-up, an icon or a color, clicked wherever it appears. This path has its own steps — what it looks like, where to look, and when it shows up — before it asks what kind of click; see below.

What kind of click? — Left, Right or Middle, then Single, Double, Triple or Hold down. Hold down presses the button once and keeps it down until the run stops — for mining, charging an attack, or holding a drag. It is not offered for something on screen, because a held button cannot be placed on a found thing.

How fast? — Relaxed (1 click a second), Fast (10 a second), As fast as possible (about 50 a second), or Custom, in clicks per second or once every so many milliseconds, seconds, minutes or hours. Not asked for a hold, which runs no loop, or for something on screen. A few spots, in order still asks it, but the pace there is set by each spot's own then wait time, so the answer has no effect.

When should it stop? — When I press F6 (your actual stop key is shown; When I stop it if none is registered), After a number of clicks or After a length of time. A hold has no clicks to count, so it offers only the other two. Whatever you pick, the stop key always stops it.

Something that shows up on screen

What does it look like? — A picture of it (drag a box around it on screen) or Its color (pick it with the eyedropper). Before you add the first one you can also add pictures from files instead; after that, more are added by capturing. Each thing you add appears as a large card — the captured picture itself, or a swatch with its color code — with a Match setting of Exact, Close or Loose, and a remove button. Add another adds more; the trigger fires on whichever it finds, up to sixteen. See Screen triggers.

Where should I look for it?

• Anywhere on my main screen — simplest, but slower on a big screen and more likely to find a look-alike.
• Inside one app window — fastest and most reliable. Choose a window from the list, and the search follows the window if you move it.
• An area I draw — drag a box around the part of the screen to watch.

When it shows up… — two questions on one step:

• How often should it click it? Every time it shows up clicks once when it appears, then leaves it alone until it goes away and comes back. Keep clicking until it’s gone is for things that take several clicks. Just once, then stop waits for it, clicks once, and ends the run — so it skips the stop question.
• If there’s more than one on screen: Click the first one I find or Click all of them.

Then What kind of click? and, unless you chose Just once, then stop, When should it stop? — as above.

Review

The last step reads your setup back as a sentence — for example "Left-click the picture every time it appears in “Chrome”. Stop when I press F6." Every underlined phrase is a link back to the step that decides it.

• Test detection (something on screen only) — looks once and marks what it finds on a snapshot of the area, with a count on each card. Nothing is clicked. If a color is not found, it shows the closest color that is there and how far off it is, with a Use button to switch to it and, where it would help, Set to Loose.
• Make it look human (same spot and a few spots) — varies the timing a little and, with One spot I pick, spreads clicks over a few pixels. It has no effect on A few spots, in order, which runs on each spot's own wait time. It starts switched on. See Humanized timing.
• Save setup, Open a setup and Start over — see Runs and saved setups. Start over goes back to the first question with your answers kept.
• Start clicking — with your stop key printed on the button.

Next time you open Auto Clicker it lands on this Review step with your last setup, ready to start.

Advanced

The full form, with the same settings under different headings: Click rate (Every… an interval, or Clicks per second, with a 40 CPS (idle/incremental games) button), Click (mouse button and click type), Where to click (Follow cursor, Fixed point with X and Y fields, or Point sequence), Stop after, the full screen trigger form, and Natural movement.

Advanced also offers what the guided setup leaves out: a trigger that gates clicking somewhere else (Keep running while one is there or Stop when one appears), a different click per picture or color, and the individual Natural movement settings.

What usually goes wrong

The measured rate is below the requested rate. The panel says so explicitly: the target app or Windows is pacing the clicks. Nothing is broken, and asking for a higher rate will not help.

It never finds the thing on screen. Run Test detection first — it shows what the search sees and names the closest color when a color misses. Then see Troubleshooting.

Nothing happens in the game. The target has to be the window in front. A title using an exclusive input path may ignore synthetic input entirely — see Troubleshooting.