Twitch Drop Auto-Claim

Auto-Claims drops, while attempting to evade bot detection and claim quickly.

יש גרסאות של סקריפט זה עם קוד מעודכן. הצג את כל הגרסאות

  • v0.13 29-04-2024
    • Wait for all mutations to finish before parsing page.
    • 0.12 may not claim correctly
  • v0.12 27-04-2024
    • Updated selector for PROGRESS_BAR which had changed again.
    • Display countdown to refresh in page title.
  • v0.11 29-03-2024
    • Fixed bug with version number
  • v0.10 29-03-2024
    • Ignore progress values over 100
    • If there is more than one Claim Now button wait 2 seconds between clicks
  • v0.8 28-03-2024

    Change selector for Claim button as 0.7 stopped working

  • v0.7 23-06-2023
    • Use current time, not this load time, to report next load time.
    • Set minimum refresh using calculated rate.
    • Check for manual refresh when testing expected increase.
  • v0.6 10-06-2023
    • Don't bother looping through mutations.
    • Don't deduct offset from refresh if there was no previous progress.
    • Increased buffer on last interval check from 10s to 30s.
    • Only set base.offset to 0 when claiming, not on all 0% reads.
    • Ensure we have a previous object on claiming, we may have just happened on 100% immediately.
    • Fixed a truthy bug checking last.progress. Now testing against null.
  • v0.5 07-06-2023
    • Minor code refactor and removed some console logging.
  • v0.4 04-06-2023
    • Now uses a fixed rate based on the rate calculated.
    • Now more fussy about progress increase. If no increase between refreshes the script will start from scratch.
    • From the second refresh on, the script attempts to decrease the base timestamp, in an attempt to most accurately calculate the exact start time, and therefore the time at which the progress will reach 100%.
  • v0.3 02-06-2023
    • Fixed bug where starting progress was not recorded on first read.
  • v0.2 01-06-2023
    • Fixed bug with rate calculation, which was using the difference in progress since last load, not since first read.
    • Changed minimum refresh amount from 1hr to 30m while testing. It may increase to 1hr again in the future.
    • Now using MIN_REFRESH constant for minimum refresh amount (in seconds).
  • v0.1 27-05-2023