-
Notifications
You must be signed in to change notification settings - Fork 120
bug with automatic drop collection #77
Comments
Read through the other issues before posting one. |
any bots that solve this problem? |
No. They are all broken. |
I forked the repo, but if you know how to install node and run NPM, you can just patch the points script to skip collecting points like what i did |
PatchesYou can also always download the forked repo and run in linux aswell. Temporal patch until a real fix is delivered., Hope this helps people in long run. |
Tried your Drop patched but it keeps closing for no apparent reason |
If fixed some more issues, you can try 00.03 from me see if that helps, make sure to do the new twitch session method aswell, and disable channel points collection [new feature i placed in] also shown how to do that |
I am also getting this error... Sad because there's Rust drops I'd like to get |
Could be an issue with your auth-token, get a new auth token using my method, worked for me and few friends that also the issue |
Yep! A fresh token fixed it. All I needed to do. |
I'm really confused on how it works for some and broken for others, wtf did twitch change in their back end, like fook. I'm looking into fixing gql-ttvdropbot and seeing what I can do with that. I'm using the program, and I want to try and contribute fixes; but its twitch going 1 step forward, 2 steps back with their code and im trying to go 5 steps ahead |
I'm using your forked version along with the instructions posted on your github page, along with (https://chrome.google.com/webstore/detail/automatic-twitch-drops-mo/kfhgpagdjjoieckminnmigmpeclkdmjm/) |
GQL RESPONSE ERROR! DropsPage_ClaimDropRewards Request Failed... Retrying in 30 seconds... Try: 1/4
GQL RESPONSE ERROR! DropsPage_ClaimDropRewards Request Failed... Retrying in 30 seconds... Try: 2/4
GQL RESPONSE ERROR! DropsPage_ClaimDropRewards Request Failed... Retrying in 30 seconds... Try: 3/4
GQL RESPONSE ERROR! DropsPage_ClaimDropRewards Request Failed... Retrying in 30 seconds... Try: 4/4
The text was updated successfully, but these errors were encountered: