But I see if I do that then re open deluge it needs to re download the missing chunk, therefore recreating a sparse file... so not as simple as I'd hoped

I never said I was removing the torrent. If I download a torrent containing four files but only select one of the files I shouldn't have to remove the excess files from the completed directory once the torrent has finished. I could go through removing the sparse files by hand find torrents_complete/...

But that leaves the job of cleaning up to the user, I would hope even an average client could do that. I would definitely expect it from the *best*.

From the FAQ:

We want to be the best BitTorrent client around, and to do that we need to focus on just being a client.

if file_selected[0] -> discard data (/dev/null, whatever) if file_selected[1] -> write to file else implode Radically oversimplified and in an imaginary language, but it certainly isn't impossible to come up with a solution to this problem. (I've got utorrent kicking round, I'll refresh my memory an...

Thanks for the link.

It is a bug. Instead of getting it behave how the user would expect there's a FAQ entry essentially telling users to lump it.

If a file is not requested by the user it should not be created.

Just to confirm I removed that torrent and data and readded it with the same selection, exactly the same result.

I too see this bug. I started a torrent that contained four files. I only wanted one and set the other three to 'Do Not Download'. I got the file I wanted and in addition to that I got 0.66% of one of the 'Do Not Download' files. Use Full Allocation is set. I installed deluge 35 minutes ago, so from...