Daffy's Mods
← All buildsApps & tools

Auto Clicker

A standalone Windows auto clicker in the style of OP Auto Clicker. One source file, one 29 KB .exe, no installer and no runtime to download — it builds against the .NET Framework that is already part of Windows.

  • 1 picture
Code not public yet
Auto Clicker, first picture

Build it with build.cmd (see below), then run AutoClicker.exe. There is no prebuilt binary in this repository.

Screenshot

The Auto Clicker window: click interval, mouse button and click type, repeat count, cursor position, and Start and Stop buttons on F6

Everything is on one window: how often to click, which button, single or double, how many times, and where.

Features

Panel What it does
Click interval Hours / mins / secs / milliseconds, all added together. Leave every box at 0 to click as fast as the machine allows.
Click options Left, middle or right button; single or double click per repeat.
Click repeat Stop after a set number of clicks, or keep going until you stop it.
Cursor position Click wherever the pointer happens to be, or lock onto fixed screen coordinates.
Pick location Press it, then click the spot you want. That click is swallowed, so nothing gets pressed for real. Esc cancels.
Hotkey F6 by default. Starts and stops from anywhere, even while another app has focus. Rebind it with Hotkey setting (modifier combinations like Ctrl+Shift+F8 work).
Always on top Keeps the window above whatever you are clicking on.

Every setting is remembered between runs in %APPDATA%\AutoClicker\settings.ini.

It will not click its own window

When you start a run and then move the mouse toward your target, the pointer crosses the Auto Clicker window on the way — and the clicker is already firing. A stray click landing on Stop would end the run after a single click.

So before every click the engine checks which window is under the pointer, and withholds the click if that window belongs to Auto Clicker. A withheld click does not consume a repeat, so a “Repeat 20 times” run still delivers all 20. The status bar says “Waiting - the pointer is over Auto Clicker” while this is happening, and clicking resumes the moment you move onto the target.

Rapid clicks and double-click detection

Windows apps decide for themselves that two clicks close together are a double-click — the threshold is the system double-click time (500 ms by default) as long as the pointer has not moved more than a few pixels. In Pick location mode the pointer never moves at all, so any interval under that threshold will be read by the target as double, then triple, then quadruple clicks. That is the receiving application’s interpretation, not extra clicks being sent; the engine sends exactly one press and one release per click and the --clicktest mode verifies that.

If you need clicks treated as distinct singles, use an interval above the system double-click time.

The status bar always shows the current interval in h / m / s / ms form, so a value like 46 m 2 s is obvious rather than hiding as a large second count.

How it works

Building

build.cmd

That invokes C:\Windows\Microsoft.NET\Framework64\v4.0.30319\csc.exe directly. The source targets C# 5 so that in-box compiler accepts it.

Tests

Five headless modes, none of which shows a window:

AutoClicker.exe --selftest    C:\path\to\selftest.log
AutoClicker.exe --clicktest   C:\path\to\clicktest.log
AutoClicker.exe --repeattest  C:\path\to\repeattest.log
AutoClicker.exe --pendingtest C:\path\to\pendingtest.log
AutoClicker.exe --guardtest   C:\path\to\guardtest.log

--selftest checks interval arithmetic, config building, hotkey display round-trips, the marshalled INPUT struct size, and settings persistence (against an isolated temp file — it never reads or writes your real settings).

--clicktest is the real end-to-end run: it installs a low-level mouse hook first, then drives the actual click engine, and swallows every injected click inside the hook so nothing on the desktop ever receives one. It aborts without sending anything if the hook cannot be installed. It verifies the click count, that Windows flagged each event as injected, that none escaped, and that measured pacing matches the target.

--repeattest drives the real Start-button code path and checks a counted run delivers exactly N clicks and hands the controls back afterwards.

--pendingtest checks a number typed into a spin box is the one actually used, even if you never leave the field before pressing the hotkey.

--guardtest is the regression test for the self-click bug: with the pointer over our own window it asserts zero clicks are sent, zero repeats are consumed and the run stays alive; then it moves the pointer away and asserts the full count is delivered.

All modes exit 0 on success and write a pass/fail report to the log path.

Notes

Status

Feature-complete and working on Windows 11. Windows only.

Built with

C# 5, Windows Forms and the Win32 SendInput / low-level hook APIs, compiled with the csc.exe that ships with the .NET Framework 4.x.

License

All rights reserved for now.

More builds

Apps & toolsGrimmicThe audiobook that reads itself, and a good e-reader too. Grimmic is a Windows desktop app for your ebooks (EPUB, PDF, TXT, Markdown) that works two ways.Updated Oct 4, 20263 picturesApps & toolsTrackBoardTrackBoard is a personal "life OS": tasks, projects, habits, school, practice, money and a journal in one web app, drawn in a hand-sketched notebook style.Updated Oct 4, 20263 picturesApps & toolsGrimmic MobileThe phone and tablet version of Grimmic: an e-reader and an audiobook in one.New6 pictures