Repository navigation
[FR] Set Force Start Automatically #1000
Replies: 2 comments 1 reply
|
I have a similar issue. In my case, download torrents that are very time sensitive. So if the something from the *arr suite adds the torrent, it will be added but may sit in 'queue' for a while and I'll miss my time window. I was more looking for a way to use 'Force Start' in a Workflow rule. This way I can add other conditions to selectively "Force Start." |
Agent BriefCategory: enhancement Current behavior: Desired behavior: Key interfaces:
Acceptance criteria:
Out of scope:
Why a human: Feature scope is a maintainer call. Two decisions sit here: whether force start belongs in the rule engine action set at all, and whether interval-bound timing answers the time sensitive case raised in the follow-up comment or whether that needs its own trigger. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe.
Not a real issue. Just a specific use case. I use a tracker that use a system of bonus points based on how many torrents are currently seeding and since how long. The problem is that without the force start option, torrents eventually return in queue, which mean the bonus points are not applied.
They also have a system to prevent hit-and-run (downloads must be seeded for at least a week or account is lock for 15 days). The regular queue have a tendency to trigger this system if I don't micromanage recently added torrents.
Describe the solution you'd like
I would like an option to automatically set torrents to force start, based the tracker.
Describe alternatives you've considered
Any other options that can make sure torrents from a specific tracker can't stop seeding.
Additional context
Otherwise, it's a great tool. Especially the cross-seed functionality!
Thank you for the work :)
All reactions