-
Notifications
You must be signed in to change notification settings - Fork 408
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
Ratio Groups Minimum Seed Time #2518
Comments
+1 from me for this idea. Workaround for now |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Is your feature request related to a problem?
It can be slightly annoying when torrents reach their ratio requirement extremely quickly (like when they first release and you are among the first to seed) and the action is triggered before other programs are able to do what they need to do with the torrent.
Describe the solution you'd like
It would be very nice to see the time column in ratio groups split into a min and max. So, regardless of what else is set, the action will not trigger until the minimum time has been reached - unless it is disabled with -1. The max would function much like the current time column does, where once that time is reached, the action will be triggered regardless of the other columns.
This would enable making sure that torrents seed for, lets say, a day before the action is triggered even if the other values have been met. This has the added benefit of increasing your upload ratio by holding onto hot torrents for longer when they reach your regular ratio requirement before the minimum time limit.
Additional context
Furthermore, it seems like even the auto unpack feature can be affected by this. I have noticed that torrents that reach the ratio rules too quickly will not be unpacked. For context, I have my default rule set to 120% and 350 hours - at which point it will mark it as finished. If this happens too quickly (could possibly be satisfied BEFORE the torrent is even completely downloaded!), it seems like the torrent does not get unpacked as it is supposed to.
The text was updated successfully, but these errors were encountered: