Autoclicker

I want a custom Windows autoclicker application (not necessarily AutoHotkey) with a modern GUI and full customization. Requirements: - Must work globally, not only when the app window is focused. - Must work while other applications are active. - Must work in windowed applications. - Must work in borderless-windowed applications. - Must work in fullscreen applications and games where possible. - Adjustable CPS and/or customizable click delays. - Support both hold-to-click and toggle modes. - Customizable hotkeys. - Profiles that can be saved and loaded. - Left-click and right-click support. - Modern GUI with settings that can be changed without editing code. - Reliable mouse state detection. Input & Binding Requirements: - Any action should be bindable to almost any input. - Support keyboard keys, mouse buttons (including Mouse4 and Mouse5), and mouse wheel up/down. - Ability to create multiple independent autoclicker slots/actions. - Each slot should have its own settings and hotkey. - Ability to add additional slots whenever needed. - For each slot, I should be able to choose what output it performs (for example: left click, right click, or another supported action). - Example: I may want Mouse5 to autoclick left click, while Scroll Wheel Up autoclicks right click, with completely different settings for each. My main issue with previous autoclickers is that when holding a mouse button to autoclick, releasing the button does not always stop clicking immediately. I want instant stop behavior with no ghost clicks, delayed clicks, or timer backlog issues. I already have a fairly large AutoHotkey v1 script that contains most of the features and behavior I want, including: - GUI with sliders and settings - Customizable hotkeys - Autoclicker mode - FastPlace mode - Scroll-based actions - Suspend key support - Adjustable delays The script can be provided as a reference so you can see exactly how I want the application to behave and what features I want to keep. You do not need to use AutoHotkey or build on top of that script; it is simply a reference implementation for functionality and user experience. I am open to C#, C++, Rust, or another suitable language if it provides a more reliable and modern solution. The application should be stable, responsive, and designed to work correctly regardless of whether the target application is windowed, borderless-windowed, or fullscreen.