As of right now deluge makes a copy of every torrent in the state folder under AppData.
I don't believe this is efficient when the option to store torrents in a separate directory is turned on.
Another issue I have noticed is that if you are loading a torrent from the same directory as the directory set to copy your .torrent files to it will replace the existing file instead of realizing that the file is already in the right place.
Running deluge version 1.3.5 with libtorrent 0.16.1
Why does deluge need two copies of each torrent?
Re: Why does deluge need two copies of each torrent?
I cannot remember if there is a reason for it.eepman wrote:I don't believe this is efficient when the option to store torrents in a separate directory is turned on.
Raise a ticket and it can be looked into, mark for 1.3.6 milestone.eepman wrote:Another issue I have noticed is that if you are loading a torrent from the same directory as the directory set to copy your .torrent files to it will replace the existing file instead of realizing that the file is already in the right place.
Re: Why does deluge need two copies of each torrent?
The copy of the torrent in the state folder gets removed when you remove the torrent while the copy in the specified torrent folder doesn't.