Deluge already has the options to "Stop seed at ratio" and to "Remove at ratio". It would be nice to see another option added that would be "Remove data at ratio" as well. I have my deluge torrents mostly managed by an external application (Flexget) and everything is working great. The only pain point is that after I set the file to be removed at a ratio, I still have to monitor the files, and then if the file no longer exists in deluge, delete the file myself. This would be extremely useful for users of seedboxes like myself. Furthermore, having this option accessible via RPC (such as core.set_torrent_stop_at_ratio works for setting if the torrent should stop at the ratio) would be extremely helpful.
Maybe I am just missing something, but I don't see this functionality yet. Is it there? Or can this be added?
Thanks!
Delete Data at Ratio
Re: Delete Data at Ratio
See Plugins
-
- New User
- Posts: 8
- Joined: Sun Sep 28, 2014 1:01 am
Re: Delete Data at Ratio
Can you be a little more specific? Also, am I able to make changes to the plugin settings via RPC calls as mentioned above?
Re: Delete Data at Ratio
If they have been decorated for export then yes e.g.: https://github.com/omaralvarez/deluge-a ... re.py#L134
-
- New User
- Posts: 8
- Joined: Sun Sep 28, 2014 1:01 am
Re: Delete Data at Ratio
It appears that the example you gave with autoremove plus is at the global level (set for all torrents). I realize I failed to mention that I want this to be able to set at a per-torrent level (much like the "Stop seed at ratio" and to "Remove at ratio" have a global option and per-torrent option). Is this possible? Or am I missing something and autoremove plus allows "Remove data at ratio" at a torrent level?
Re: Delete Data at Ratio
Use labels
-
- New User
- Posts: 8
- Joined: Sun Sep 28, 2014 1:01 am
Re: Delete Data at Ratio
I am already using the labels to determine other functionality.
I am curious why this isn't just a true/false flag in the torrents.py file just like the stop_at_ratio and remove_at_ratio bool. Is there any reason this is not implemented this way?
I am curious why this isn't just a true/false flag in the torrents.py file just like the stop_at_ratio and remove_at_ratio bool. Is there any reason this is not implemented this way?