Closed jordyamc closed 2 weeks ago
Hello,
Hmm. I've taken a look at the code, and it seems that the chain of calls is: TimedDrop.availability -> BaseDrop._base_can_earn -> TimedDrop._base_earn_conditions
, which verifies that self.required_minutes > 0
. However, availability
checks self.total_remaining_minutes
- the wording implies it's a different variable, required vs remaining. A drop with required_minutes > 0
and remaining_minutes <= 0
is any drop that has been finished mining, so these are possible.
I've reworked the availability
method a bit, and it shouldn't cause an exception anymore. I haven't tested it though, but it should work: https://github.com/DevilXD/TwitchDropsMiner/commit/93d5d8750d9bdb5cc7749d755e9a75d659a8cb30
Please verify that everything works now.
I'm assuming that the fix worked, and this issue has been resolved by now.
It seems the method is not checking total_remaining_minutes