Page 1 of 1
move on completed - not until seed ratio is met?
Posted: Fri May 22, 2015 2:52 pm
by Symbiot
hi
am I doing something wrong, or am I missing the point..
From othe bittorrent clients I'm used to setting "move on completed" and usually that means, as soon as torrent changes from downloading to seeding, the files are moved to the location I've set.
but so far, in deluge, it seems to not do that
finished torrents stay in my temp folder...
How can I change this behaviour to "move on download completed" and continue seeding from finished location?
Re: move on completed - not until seed ratio is met?
Posted: Fri May 22, 2015 5:39 pm
by Symbiot
if I set "move completed" in the "main" menu it seems to work.
if I untick that and use the "autoadd" plugin then it doesn't move the files to my "completed" folder.
What could be wrong?
Re: move on completed - not until seed ratio is met?
Posted: Fri May 29, 2015 6:26 am
by RobC
I'm having the same problem. I have move on complete checked in my autoadd rules, and directory set. Once torrent is added I can see in the torrent options it is not getting set.
Re: move on completed - not until seed ratio is met?
Posted: Sat May 30, 2015 10:24 am
by RobC
Well I found my problem, If you don't have move on complete set up for all torrents in the "prefrences>downloads" move on complete doesn't seem to work from autoadd. Set that up and it starts working. Now I'm not sure if this is a bug or what but if anything else autoadd show not let you set up move on complete unless it is set in the "prefrences>downloads" with a message telling users they need to set that first to allow move on complete to work in autoadd.
Re: move on completed - not until seed ratio is met?
Posted: Sun May 31, 2015 10:03 pm
by RobC
Problem with Move on complete popping back up again and the move on complete set from auto add is getting overwritten by the default or not getting passed along. For now if fixed this by haveing autoadd set a label and setting up label with move on complete which seems to be working now.
Really curious if anyone else has run into similar problems. I think I started noticing this when I updated to 1.3.11 a few week ago. I installed plugins around the same time so it could be one of those.