New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop watching the channel if the drop is claimed #418
Comments
Same issue here. |
Same issue here! |
Ah this actually explains the issue I've been experiencing where it seems as if the miner is ignoring my priority list completely. I tried setting get followers to False and manually inputting every streamer into a priority list but it keeps going to these two streams that are low on my priority list. Checked today and found out they have drops enabled. However, I've already completed and claimed these drops 10 days ago so the miner is farming the wrong channels. |
Same issue here! |
Seeing this as well, It watched the channel and got all the drops but stayed watching the channel even though all drops had been claimed and it was lower in the list then other channels that are live, restarting the container does not change anything in this case Happens as soon as a channel with drops goes live even if all have been claimed. Needs to be a check i think to see if all drops are claimed, if they are then either switch to another channel with drops or if all drops are claimed to go back to to the order list, Mine is set the same Priority order |
Same issue here! |
if drops are least of my concern, should i remove the drop line or put it to the end like this Priority.STREAK, |
Is your feature request related to a problem?
At the moment if we have the priority set like this:
priority=[
Priority.STREAK,
Priority.DROPS,
Priority.ORDER
Then if any stream has drops enabled, it is watched all the time, even though the drop has been claimed and is last on order list.
Proposed solution
Would it be possible to add an option if a Drop has been claimed and the stream continues, to set the script to switch to Priority.ORDER and not continue watching the channel with the Drop it has already claimed.
Alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: