Auto-Claims drops, while attempting to evade bot detection and claim quickly.
当前为
On page load the script will look for any progress bars, and select the bar with the largest progress value.
If the progress is 100% it will attempt to claim the drop. It will then reset it's recorded progress to 0% and record the current time.
The first time the script finds a progress bar it will record the progress value, and the current time.
To start, the refresh rate is based on a 30m drop, so the script will first refresh the page assuming it will be a percentage of that time.
On page load the script will check whether it has a record of a previous read. If so it will calculate the amount the progress has increased, and the time that has passed, since the previous page load. It will then recalculate the next page refresh depending on that rate of change. It will however limit the refresh rate to 30m, as the progress rate calculation will always be more accurate later in the process (when the calculation has the largest time interval and progress change to calculate the rate more accurately), and we want the final refresh to occur soon after 100% has been reached.
In this manner the script will limit the page refreshes it makes, so as not to trigger bot detection, which I was experiencing with other scripts. It should also claim the drop soon after it is available, as it has previously approximated when the progress will reach 100%.
