-
Notifications
You must be signed in to change notification settings - Fork 120
GQL RESPONSE ERROR! ClaimCommunityPoints Request Failed... Retrying in 60 seconds... Try: 1/4 #83
Comments
this bot no longer works. |
The basic core functionality works, it's just a pain to set up. Use this fork and add |
This fork gives the same errors as the main repo |
You probably forgot the step of modifying the settings.json |
Having same issue |
This version and that setting are working for me. Thanks! |
Watching stylishnoob4 | Points: 10
Current Progress: 25 % | Watched 30/120 Minutes | Drop 1/2 | Status Active | isClaimed false
Current Progress: 0 % | Watched 0/240 Minutes | Drop 2/2 | Status Active | isClaimed false
Watching stylishnoob4 | Points: 20
Current Progress: 26.67 % | Watched 32/120 Minutes | Drop 1/2 | Status Active | isClaimed false
Current Progress: 0 % | Watched 0/240 Minutes | Drop 2/2 | Status Active | isClaimed false
Watching stylishnoob4 | Points: 20
Current Progress: 27.5 % | Watched 33/120 Minutes | Drop 1/2 | Status Active | isClaimed false
Current Progress: 0 % | Watched 0/240 Minutes | Drop 2/2 | Status Active | isClaimed false
Watching stylishnoob4 | Points: 20
Current Progress: 28.33 % | Watched 34/120 Minutes | Drop 1/2 | Status Active | isClaimed false
Current Progress: 0 % | Watched 0/240 Minutes | Drop 2/2 | Status Active | isClaimed false
Watching stylishnoob4 | Points: 20
Current Progress: 29.17 % | Watched 35/120 Minutes | Drop 1/2 | Status Active | isClaimed false
Current Progress: 0 % | Watched 0/240 Minutes | Drop 2/2 | Status Active | isClaimed false
Watching stylishnoob4 | Points: 20
Current Progress: 30 % | Watched 36/120 Minutes | Drop 1/2 | Status Active | isClaimed false
Current Progress: 0 % | Watched 0/240 Minutes | Drop 2/2 | Status Active | isClaimed false
GQL RESPONSE ERROR! ClaimCommunityPoints Request Failed... Retrying in 60 seconds... Try: 1/4
GQL RESPONSE ERROR! ClaimCommunityPoints Request Failed... Retrying in 60 seconds... Try: 2/4
This error always occurs after running for a while.
The text was updated successfully, but these errors were encountered: