I should preface this by saying that this is most useful when migrating from one torrent client to another, but in general, it's the default setting that I've become accustomed to in uTorrent, and I at least think it should be an option in Deluge.
I am adding many previously torrents in my seed collection to Deluge, but I didn't download every file of every torrent. I added them in the paused state, found the proper download locations, and started re-checking them. It would have taken me a few minutes just to watch the first torrent re-check, let alone dozens, so I went and did something else. When I came back to Deluge, I see that it's downloading data and re-allocating space for tons of files that I never wanted.
It took me a significant amount of time to clean up the mess, and now adding more torrents is becoming a tedious process. I have to mark every file as do-not-download, then re-check, then mark the ones I actually have as normal. This is instead of re-checking to paused state, then marking the ones I don't have not to download. Basically, the process is twice as long as it could be.
Unless there is an alternative that I'm missing, I would like to submit this as a feature request.
Feature req:configure default to paused state after re-check
Re: Feature req:configure default to paused state after re-c
I'd suggest creating a new ticket: http://dev.deluge-torrent.org/newticket
Re: Feature req:configure default to paused state after re-c
I've done a few tests and I believe that even though files are marked as 'do-not-download,' if deluge has verified chunks, it will seed them. If that's the case and that's functioning as intended, then I really don't think I need to submit a ticket.
I just want to verify this is as-intended that any complete chunks, regardless of file download priority, are seeded, or if it's a weird side effect.
I just want to verify this is as-intended that any complete chunks, regardless of file download priority, are seeded, or if it's a weird side effect.