Setting the Click Interval in Auto Click Draco

The click interval is the single most important setting in Auto Click Draco. It defines how much time passes between each automated click that the app sends to your Mac. Every other feature — stop conditions, start delay, stationary detection — sits on top of this timing decision.

In Auto Click Draco the interval is measured in seconds, with a minimum of 0.5 seconds (two clicks per second) and a maximum of 3,600 seconds (one click per hour). The range was chosen deliberately. Anything faster than 0.5s starts to look unnatural to most software and can be flagged as bot input. Anything slower than an hour is better handled by a real scheduler.

A shorter interval means faster clicking, which is useful for incremental games, stress testing UI, or quickly burning through repetitive prompts. A longer interval is better for keeping a session alive, refreshing a dashboard, or triggering a workflow on a slow cadence so you don't get rate-limited.

Open Auto Click Draco and find the Click Configuration card near the top of the window. The Click Interval field accepts decimal values — you can type 0.5, 1, 2.5, 15, or 600. Use the up and down arrows next to the field to step the value by 0.5 seconds at a time, which is the smallest increment Auto Click Draco supports.

Once you've entered a new value, press the Update button. This is intentional: Auto Click Draco only commits the new interval after you confirm it. The reason is safety. If a click loop is already running and you nudge the field by accident, your session keeps using the previous interval until you explicitly press Update. The summary panel on the right side of the window will reflect the new value the moment it's applied.

If the Update button is greyed out, it means the value you typed is identical to the one already in use, or it's outside the supported range. Clear the field and try again with a value between 0.5 and 3600.

For idle and incremental games (Cookie Clicker, Adventure Capitalist, Melvor Idle, and similar), 0.5 to 1 second is the sweet spot. It keeps progress healthy without spiking CPU usage or triggering anti-cheat heuristics that look for inhuman click rates.

For productivity tasks like keeping a meeting tool, chat app, or remote desktop session marked as active, 30 to 120 seconds is plenty. Most apps consider you idle after 2–5 minutes, so a click every minute or two keeps your status green without causing any visible activity.

For long-running schedules — refreshing a live dashboard, polling a status page, or keeping a long-running web form from timing out — a value of 300 to 600 seconds (5–10 minutes) works well. This is gentle on servers and avoids unnecessary network chatter.

For UI testing and stress tests, the 0.5–2 second range gives you predictable, repeatable input you can pair with the Stop After condition to fire an exact number of events.

If you're unsure where to start, use 1 second. It's a safe default that works for almost every scenario. Watch the click counter in the status panel for the first 10–20 clicks to confirm the rate matches your expectations.

If clicks feel too fast, double the interval. If they feel too slow, halve it. You don't have to stop the session to retune — just edit the field and press Update again. The current loop will pick up the new interval on the very next tick.

The most common mistake is forgetting to press Update after changing the field. If the summary panel still shows the old value, your edit hasn't been applied yet. Press Update once and you'll see the change reflected immediately.

The second most common mistake is setting the interval too low for the target app. Many games and websites detect clicks faster than 5 per second as automated input. If you see your clicks being ignored or your account flagged, slow the interval down to 1 second or longer.