NIAutoclicker is the one autoclicker (That I know of) that doesn't completely halt whatever you're doing. After setting the click location, you can navigate to a different window, or even play a different game, and the autoclicker will continue to click, just as if you were still there.

As an additional tweak, you can also click in-game, and user inputs will take precedence. This lets you navigate menus and level up heroes, with the autoclicker still running, and without any severe hiccups.

Also added, you can change the click frequency as you like. I've found that if it's too fast, the game itself lags, and you won't be able to click on much with it running. So as a default, I have it set to 50 clicks/sec, which seems to be about the highest I can get without lag, and still allow smooth user clicks. That could just be my system, though, so I've added this small bit of customization.

Raw AutoHotKey script: http://pastebin.com/yLJEbMxP

(Windows only, x64 and x32 versions included)
Downloads available at GitHub: https://github.com/Shadowspaz/NIAutoclicker

First and foremost, Steam doesn't even care. This is not a VAC-enabled game, and as such, does not have the capability of detecting any cheating, be it with autoclickers, Cheat Engine, or straight up modifying the game files.

But this is a singleplayer game, and as such, there aren't even any services that the ban would apply to, since VAC is specific to servers.

But aside from that, even, there is no way to reliably detect an autoclicker. It would fall into the category of macros and turbos, and those are common in hundreds of programs and peripherals.

To put it simply- Autoclickers are too challenging to police, and too inconsequential to even bother with.

Besides, a lot of people just use autoclickers to save their mouse. And if you decide you want to do that, and keep things fair, you could set it to 8-10 clicks/second or so. Something you can personally do, but don't want to damage a mouse to do it.

It is not detectable, and even if it were to be running while you're playing a VAC-enabled game, this autoclicker is ONLY clicking in the window you set it to. So if you have this running in CH while playing CS:GO, they have absolutely no way of telling.

If the autoclicker runs fine for you, and then starts lagging, you can get it running smoothly again. Hold left-click in the active window until the autoclicking stops and it all catches up. Then drag outside of the window, and immediately click again.

For whatever reason, this removes all the lag, and leaves it running smoothly again (Assuming it could run smoothly before).

If I can figure out why this works, I can work it in, and virtually all lag will be removed. For now, though, this is the trick.

Run NIAutoclicker as administrator.

(Right click > Run as administrator)

(As of 1.5.1, You can check your version number in the options window)

• 2.1.1 - Fixed occasional "hotkey overflow" bug
  
• 2.1.0 -
  • Added support for multiple click locations
    
  • Toggle hotkey no longer requires you to reset location(s)
    
  • Added "Reset" button to options
    
  • Changed options hotkey to ( Alt + - ) instead of (Alt + = )
    
  • Add an "exit on target window close" prompt
• 1.5.2 - Clickspeed GUI now displays the same number you typed in, and saves each number for CPS and SPC
  
• 1.5.1 - Slight tweak to click handling- May improve click recognition when setting click location
  
• 1.5 - Improved "Change speed" GUI- Now allows for clicks/second, or seconds/click
  
• 1.4 - Improved user click detection- Now more reliable during runtime
  
• 1.3 - Increased performance speed and reduced memory usage
  
• 1.2 - x32 and x64 release. Also included the option to change clickrate
  
• 1.1 - Added user input preference. Click while autoclicking
  
• 1.0 - Initial release

For discussion and comments, check out the original thread: http://sp.zhabite.com/app/363970/discussions/0/613958868350366276