qBittorrent official forums

Is there a setting to move completed files? I like to keep my incomplete files on one drive and when completed move to another drive so my tv can access it.

Also is there a manual someplace that gives info on all the features/settings?

Thanks for any help.

Just found out how to move completed files manually, still want to have it move automatically if it's available.

It's right in the "Downloads" of Settings.

"Save files to location:" This will be the "WHERE TO MOVE DOWNLOADED".
"Keep incomplete torrents in": This will be the "WHERE UNDOWNLOADED IS."

You have to tick the box at the "Keep incomplete torrents" text.

Manual?
Well, check out each tab in Settings and such. If you are looking for some feature and can't find it, make a question here.
Manuals take a lot of time to write and maintain. And then only a person stumbles upon it who pressed F1 by accident.

But there is a WIKI! That could also help you master qBittorrent.
https://github.com/qbittorrent/qBittorrent/wiki

Be careful when using the "Keep uncompleted torrents in" setting.  This has undesireable side-effects when trying to add existing torrents and data to a tracker.

Thanks for the quick response.

@shiki - maybe I'm not understanding this. I did fill in that box "Save files to location:" to put my initial torrent/file, are you saying that should be where it moves to after completion? If so then how to change default initial downloading file as I don't want it in c: drive or user section. I have a specific hard drive just for torrents downloading, and another drive for only completed torrents which can be accessed by other devices. I do it this way because both downloading and seeding drives are constantly reading/writing. Maybe I'm still misunderstanding because "Keep incomplete torrents in" is also for files as well as torrents?

@Muzak - That is my setting, what undesirable side effects are you speaking of?

Update
Ok, had a chance to play around for a while.
On initial drag and drop pop up window, the default is my completed folder, so it's a bit confusing as to what it's asking for, there is a drop down box giving me a choice for incomplete folder and completed folder. Initially I choose incomplete folder, which doesn't move the files after completion. Maybe word it differently so it's not as confusing?

Also in the settings, maybe changing the order and/or wording of "Save files to location" and "Keep incomplete torrents in" would make it less confusing. Such as "Save completed files" Also keeping the nomenclature the same would help as well. Torrent and files are synonymous, yet throwing in a dot as in .torrent is not, so using those terms with the dot and without the dot can be a bit confusing. On the same token is there a way to increase the font size?

On deletion - only the .torrent file in user folder is deleted. On checking "Also delete the files on the hard disk" only the .torrent file in user folder is deleted. Is there a setting where .torrent file in the incomplete folder and the completed folder can be deleted as well?

Thanks.

one last question, I have many more questions as the wiki didn't answer some things. Should I post question individually or can I group it into one thread?

Thanks again.

qBit gets confused sometimes about where the data is when that option is checked.  sometimes it will try to move the data back to the "incomplete" folder and then decide it's complete, but leave it in the incomplete folder, sometimes it just decides to re-download the torrent regardless of the existing data and in very rare circumstances (2 times out of a couple hundred) will both move the data and then reinitialize the files and download, wiping out the original data.  In my case for these two torrents, there were no seeders anymore and I lost the data.  Not a big deal, but makes me very careful and a bit superstitious about each step to make things work right.  I've simply turned the option off because of it's current state.

It would be much better to have an option to put *new* downloads into a specific folder that then would move to the "completed" folder.  When torrents are pointed to existing data, just recheck in place, never move it whether it's complete or not and let the user decide if they need to re-download the changed/missing data or just leave the torrent paused.  This would mimic the behavior of uTorrent making the transition from uT to qBit easier for the casual user.  IMHO, qBit is extremely close to being *the* replacement for uTorrent with private trackers.

http://qbforums.shiki.hu/index.php/topic,2555.0.html,

But that's a linux issue why would I read that???   

Thanks Muzak, I'm currently in testing mode so all the files are not a problem, currently downloaded a couple of gig and watching, nothing untoward so far with those settings checked. Maybe you can give additional details? Such as how long you were seeding, public or private tracker, etc.

Since shiki hasn't posted back on what is acceptable in posting, ie grouping multiple unrelated questions together, I'll take a chance and post everything that I don't get or don't know how to do.

It's the same base source code for all operating systems and the same libtorrent libraries, anything that affects the basic operations in one is equally likely to affect another.

@ciaobaby, I understand, was making a poor attempt at humor.

@lookingglass  I'm (slowly) working on importing several hundred torrents that I previously downloaded from private trackers, some were still active on the tracker, many needed to be reposted to the tracker and then added.  In all cases the valid data for the torrent is already on my RAID array.  With the number of torrents I really don't want to move them to the uncompleted folder to have qBit check them and move to the completed folder and then have to move them back to their original location.  I just want to point qBit at the data.  There are some (known) issues with how qBit handles this situation and one thing that makes a huge difference is to turn off the uncompleted folder.  The devs know about the issues and hopefully 3.2 will address them.