Nazar1ky
commented
1 month ago Even better, there's
message.type"drop-claim"which triggers instantly when stuff is claimable, and contains adrop_instance_idI put the claim GQL request there and it works flawlessly
{"type":"MESSAGE","data":{"topic":"user-drop-events.UserId","message":"{\"type\":\"drop-claim\",\"data\":{\"drop_instance_id\":\"DropInstanceId\",\"drop_id\":\"DropId\",\"channel_id\":\"ChannelId\"}}"}}
How you see that? I see only drop progress updates.
Describe the bug
Since a few days (somewhere in between last friday and yesterday) the miner started having problems with the auto claiming of drops. I thought at first this was a problem of the latest release so I temporarily reverted back to 1.8.3 with the same problem. It seems though that there's only a problem while the script is running, restarting the Miner (and having set claim on startup variable) will do the claim fine. Am I the only one having that problem or is there something with the Script/Twitch API?
Thanks!
Steps to reproduce
1) Start the Miner with config file 2) Watch a Streamer with Drops on 3) Drop will Progress, however not be claimed automatically while the script is running
Expected behavior
Claim Drops automatically like it used to until a few days ago when having 'claim_drops=True' set
Operating system
Docker on Synology NAS
Python version
Docker on Synology NAS
Miner version
latest
Other relevant software versions
No response
Logs
https://gist.github.com/pchristod/1d40e20200023768a3e057167b435622
Additional context
I've tried to capture the issue by starting some random drop campaign and setting the log to Debug (see the ling to the gist). The Drop named 'Necroghouly Wraith' is still sitting unclaimed in my Inventory.