Hacker News Reader

apparently the naive solution for a script is to press the button when the desired second hits, but because the timer doesn't reset immediately, the button is pressed many times automatically. The server can tell that the button was pressed more times than a human would do it, so can mark that person as a cheater.

View on HN

How effective could it be to set up a prep program that you can use to record both the time between two clicks and the duration of each click? Then take a few runs with at that to get some average case scenarios and implement those times into the auto-click script? Then depending on when the server counts the press (first click or second click), account for the difference in time between your target time and when to execute the double click.

You could easily avoid that by stopping the script as soon as the button is pressed a single time.

indeed. The problem, I think, is that most people implement the naive solution before they realize that it's the naive solution. As each person gets only one click of the button, a lot of people don't get the chance to implement that easy fix -- they get it wrong once, and don't get to ever get it right later.

Reply on news.ycombinator.com