We will change the way we handle the Input messages received in our application, starting to use the concept of Raw Input (Win32 API). The implementation of the proposed solution is quite simple. With that in mind, what we should do is filter out these Input messages received in our application, limiting them to only reliable devices and that they originate from hardware, and not virtual messages (which are sent by software). That is, all messages are valid regardless of where they are coming from for our application.

The problem we have when trying to avoid this type of cheating in a 'native' way, is that we were unable to identify the source of a message using the Win32 API. In the case above, we are sending a WM_KEYDOWN message, e.g., a key is being pressed and with the WPARAM being VK_RETURN, means that we are simulating the pressing of the Enter key.Īs explained, you can replicate this operation for other types of events and build your own logic, like building a Bot to automatically use skills in a game. SendMessage(hTargetWindow, WM_KEYDOWN, VK_RETURN, 0) In uMsg we specify the identifier of the message we are sending (Eg WM_KEYDOWN), and the other parameters are additional information related to that type of message. In the first parameter we specify the HANDLE of the target window.

This can be done using the Win32 API's SendMessage function:Įnter fullscreen mode Exit fullscreen mode The most common method is to send an Input message to the HANDLE of the window that we want to simulate the click or keystroke. Usually, the operation of these tools is quite simple. This kind of “cheating” can be very harmful to your application, since the user is having an advantage over other players and he can set the “Bot” playing for him 24 hours non-stop (which would be very difficult for us humans). This type of auto-clicker is fairly generic and will often work alongside any other computer program running at the time and acting as though a physical mouse button is pressed. All of this can be done by simulating clicks or keystrokes.Īuto clickers can be as simple as a program that simulates mouse clicking.

These tools that simulate Input events are usually used to create Bots, where the tool will repeat a user-defined input pattern (mouse or keyboard) without having a 'real' interaction with the application, e.g., the tool will simulate behavior as if a person is in charge.Īlright, but where does the user use this type of tool? It is very common to use it in games such as RPG, where the player needs to use a skill every time, a potion to recover its life or even click on a certain position on the screen to attack a monster. Still on the topic of cheating and as a follow up on my last post in this community, I will try to explain one of the alternatives I used, and that you can also try, to avoid using tools that simulate mouse clicks or keyboard keystrokes.

Keyboard autoclick