Closed patrat46 closed 2 years ago
Hello! And oops, I commented that line out for debugging and never put it back. I will fix it now, but it's nothing critical, so there is no big need to download new release. Thank you for report!
confirmed, without this line it will send keypress every 10s.
Binary is updated now. Updating is not mandatory as there are no negative effects from sending keypress that often, other than very negligible amount of extra cpu load.
In AntiAfkKick/AntiAfkKick.cs in the current revision (16 days old) https://github.com/Eternita-S/AntiAfkKick/blob/44e3b75e2d31c94384b555492488fecabbc82816/AntiAfkKick/AntiAfkKick.cs
Below is the code referencing the tick and the next key press. The way it is writting Next Key Press is never updated from 0 This means that the if (Native.GetTickCount64() > NextKeyPress) will return true 100% of the time.
The if statement is then not needed, the variable is also not used, and the rest is determined by the thread being inactive for more than 1 minute.
Sorry to bug you, I'm mostly just curious.
The code is essentially the same this way right?