Auto Clicker: Real Clicks & Sequences

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. ─…