[rowanG077]

7ms is enough. But that is one in a chain of latencies. 110ms is way too long if you want your trigger to be effective. In 110ms the enemy has moved out of your crosshair. Humans deal with that with dynamic adjustment but the AI will just click the mouse. I'd think you'd need to hit less then 25ms end to end and even that might not be enough for far away targets.

[xxs]

I mentioned earlier - reaction time under 100ms on track events is considered a foul start and the offender disqualified.

[rowanG077]

You are completely misunderstanding the goal of such a cheat. It's a "triggerbot" as in it fires the mouse when an enemy head enters the crosshair. The classical use case is that the user camps at an edge and waits for the enemy to peek. The user has his crosshair at the correct offset from the edge so that when the enemy peeks he could hit them with a human reaction time.

However a human sees the enemy BEFORE it enters the crosshair and estimates and corrects when the enemy will enter the crosshair. A trigger bot measure exactly WHEN the head is in the crosshair, it has no predictive power of enemy dynamics. This totally changes the latency game. A 150ms trigger latency from the time a head is in the crosshair basically means you shoot when either the crosshair or enemy has moved significant amounts. This also means that you can very obviously cheat with a trigger bot if you use the trigger badly, the human needs to "hide" the trigger latency to make it appear human. You can't compare it to human reaction time at all, a trigger needs to be about an order of magnitude faster to be useable.