Auto Clicker: Real Clicks & Sequences

Auto clicker that actually registers — even on canvas games and strict controls. Build a sequence, or record it once and replay it.

Most auto clickers have the same problem: the counter climbs, but the page never reacts. That is not something you can fix by trying harder. A normal extension can only fire synthetic events, and those carry isTrusted = false. Games, click-speed tests and any control that checks for real input simply ignore them. You end up watching a rising number while nothing on screen happens. Precision Auto Clicker gives you a second engine that does not have this limitation — and unlike the single-point clickers it was built from, it runs a real sequence of steps. ── TWO ENGINES ── Precise engine Sends input through Chrome's own pipeline, so it arrives as genuine mouse input rather than scripted events. These are the clicks that land on click-speed tests, on canvas and WebGL games, and on controls that reject anything synthetic. Light engine Dispatches a full pointer and mouse event sequence from the page itself. No debugger attachment, no browser notice, and the right choice for ordinary forms and buttons. Switching engines never changes what a step does. Both engines implement every step type. If the precise engine is unavailable, the extension says so rather than silently doing nothing. ── A SEQUENCE, NOT ONE POINT ── Add as many steps as you need and they run in order, one after another, then loop. Four kinds of step: • Press / Hold — press one point and keep it down for as long as its hold duration says (0 means press and release in the same instant) • Swipe — drag from one point to a second point, with a real travel path • Scroll — turn the wheel at one point, up or down by the amount you set; a page with its own scroll area (or a map) scrolls that instead of the whole page • Follow cursor — ignores any stored point and acts wherever your mouse is, at the moment the step runs Every step has its own timing: • wait after this step (shown on the next step as "wait after previous" — the same number, so the two can never disagree) • hold duration — how long the button stays down • random offset, so repeated presses are not pixel-identical • random delay, so the rhythm is not machine-perfect With every wait and hold at 0 the sequence runs as fast as the engine allows — thousands of presses a second on the light engine — rather than being paced by the extension's own bookkeeping. ── ONE SWITCH FOR THE WHOLE THING ── The power switch at the top of the popup turns the extension off. Off here means off: the content script is unregistered, so pages loaded afterwards do not load it at all — no toolbar, no markers, no mouse tracking, nothing parsed into the page. On a page that already had it, turning the switch off removes the toolbar it drew and detaches every listener it attached, including the mousemove and scroll handlers that otherwise run on every pointer movement and every scroll. There is no "off but still watching". The cost of an extension you are not using is the reason the switch works this way rather than just hiding the toolbar. Turn it back on and it comes back immediately, in every tab you already have open — no reload needed, and no restart of the browser. ── YOU CAN SEE AND MOVE EVERYTHING ── The step list shows every step you have added, numbered, with its point and timing. Drag a row up or down to change the order and the numbers follow. Right-click any row — or any marker on the page — to open its parameters in a small window you can drag anywhere; the window closes again when you click elsewhere. Each step is drawn on the page with its number beside it, clear of the exact point it acts on. Both ends of a swipe are draggable and move independently, so a gesture can be reshaped one end at a time. A scroll step shows its direction and amount under its marker. A follow-cursor step gets a dashed, pulsing marker of its own — nothing like the X that marks a fixed point — which can be dragged out of the way and leaves the point it acts on completely alone. Nothing that destroys work happens by accident: removing a step or a saved sequence needs Shift held, and the button changes colour while it is. The toolbar itself is the drag handle — press anywhere on the bar and move it, and the buttons still work, because a press only becomes a drag once you actually move. Hover any toolbar button and a tooltip tells you what it does and which key is bound to it. There are no unlabelled mystery buttons and no wall of text on the page. ── A TOOLBAR THAT STAYS OUT OF THE WAY ── • drag the toolbar by any part of it — the buttons still work, because a press only becomes a drag once you actually move • it remembers where you put it • collapses to a slim bar, or hides entirely and comes back from the toolbar icon • live action counter and actions-per-second readout • markers can be hidden in one click, so you can see the page without them • while a sequence is running the markers stop intercepting the mouse, so your own clicks still work The play button responds the moment you press it, not when you release — which matters when a sequence is running at full speed and you want it to stop. ── SETTINGS LIVE ON THE PAGE ── There is no separate settings tab. Engine, loop behaviour, start delay, cycle limit, marker visibility, hotkey bindings and Pro activation all open in a small draggable window over the page you are working on, so you never lose your place. ── SAVE AND SHARE SEQUENCES ── Save the sequence you are working on with one press and no dialog; the saved list names it for you. Each saved sequence can be applied, overwritten with the steps you have now, shared, renamed (double-click its name) or deleted — and the two destructive ones need Shift held. Share it as a `PAC-` code: the whole sequence travels inside the code, so it works on a machine that has never spoken to ours, and it imports the same sequence on the other end. Or export a `.pac` file (plain JSON inside) and import it anywhere. A file that is not one of ours is refused with a reason instead of half-loading. ── HOTKEYS THAT DO NOT FIGHT YOUR KEYBOARD ── Bind start/stop and add-step to whatever you like, including bare function keys. Ordinary keys require a modifier, so the extension never swallows your typing, and hotkeys are ignored while you are in a text field. Rebinding takes effect immediately on pages that are already open. ── FREE, AND WHAT PRO ADDS ── Free, permanently: unlimited steps, every step type, both engines, hotkeys, the full marker and list interface, and five saved sequences. No click quota, no time limit, no nag screen. Nothing about the free version makes the product worse at the thing it is for. Pro adds: • unlimited saved sequences • an auto-stop timer, to end a long session after a set number of minutes • every future update Two ways to pay, for exactly the same features: • Once — $9.99, and it never expires • Subscription — $19 a year, cancel any time Both unlock the same list. There is one build, so a subscriber does not get a different feature set from someone who paid once; the difference is only whether it ends. Buying once works out cheaper after about seven months. It is charged yearly rather than monthly because of how payment processing works: the card processor takes a fixed fee per transaction on top of a percentage, and on a small monthly charge that fixed fee alone would be most of a third of the price. A year spreads it once across twelve months of service, which is why there is no monthly option. ── PRIVACY ── The extension collects nothing. No analytics, no accounts. Your settings, steps and saved sequences are stored locally in your browser and never leave your device. If you never enter a licence, it makes no network requests at all. Two things worth being precise about, because a subscription is involved: • A one-off licence is verified on your machine — it is a signed key, and the signature is the proof. It contacts our licence server once, when you first enter it, and never again. The reason is that a key which can be verified entirely offline also cannot be limited, so one buyer could publish theirs and anyone could use it; a one-off licence now works on three devices, and counting them needs the server. The only things sent are the key and a random identifier for your browser profile, generated by the extension and derived from nothing about your machine. After that one exchange it works offline forever, and a failed attempt uses nothing up. • A subscription is checked against Dodo Payments about once a week, since only they know whether it is still being paid for. If the check cannot go through, it keeps working for two more weeks. • A subscription licence is checked against our payment provider (Dodo Payments), because only they know whether a subscription is still running. The key is checked when you enter it, then about once a week. That is the only network request the extension ever makes on its own, it sends nothing but the key itself, and if the check cannot go through the subscription keeps working for two more weeks — being offline or behind a firewall will never switch off something you paid for. • A subscription's end date is checked against this device's clock, not against a server — there is no server to ask. That is why the extension works offline, and it is also the one thing this design gives up: a clock set backwards could in principle be used to stretch a subscription. The extension keeps a record of the latest time it has ever seen and checks the end date against that instead of against today, so winding the clock back does not extend anything. If you set your clock forward and then back again, you may see the remaining time reported conservatively — the honest direction to be wrong in. • The buy buttons open the store in a new tab. That is the only way this extension ever reaches the network, it happens only when you click it, and the extension itself sends nothing. • Switching the extension off removes it rather than hiding it: the script is unregistered, so pages you open afterwards load nothing of it at all. That is not about privacy policy, it is about not paying for something you are not using. Permissions, and why each one exists: • Read and change your data on all websites — the toolbar has to appear on whichever page you want to click on, and the light engine dispatches events into that page. The extension does not read page content. • Access the page debugger backend — used only while the precise engine is running, so mouse input can be generated through Chrome's input pipeline. Chrome attaches it when you start and detaches it when you stop, and Chrome's own "debugging this browser" notice is visible during that time. Use the light engine if you would rather that notice never appears. • Storage — to remember your settings, steps and saved sequences. • Scripting — to place the toolbar on a page that was already open when the extension was installed.