You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do not automatically move previously completed torrent to the incomplete folder after a check.
Use case
When cross seeding torrents, one torrent is complete, the new torrent added is be the cross seed.
If the new torrent matches, the torrent is complete, and cross seeding is successful.
However, it is possible the newly added torrent is not exactly the same, despite same name and size.
In this case, QBT should:
Do a check to see if the two files are exactly the same.
If checksums do not match, put added torrent into "error" status.
Do not attempt to start new torrent.
Do not attempt to move new torrent to "incomplete" folder. As this will also move the completed torrent too.
QBT automatically does #4 after the check. This moves the completed torrent.
Sometimes the last remaining amount is 16MB, and isn't worth moving the file.
I rather see the torrent go to error status, and allowing me the opportunity to rename the folder and/or file.
Extra info/examples/attachments
No response
The text was updated successfully, but these errors were encountered:
Suggestion
Do not automatically move previously completed torrent to the incomplete folder after a check.
Use case
When cross seeding torrents, one torrent is complete, the new torrent added is be the cross seed.
If the new torrent matches, the torrent is complete, and cross seeding is successful.
However, it is possible the newly added torrent is not exactly the same, despite same name and size.
In this case, QBT should:
QBT automatically does #4 after the check. This moves the completed torrent.
Sometimes the last remaining amount is 16MB, and isn't worth moving the file.
I rather see the torrent go to error status, and allowing me the opportunity to rename the folder and/or file.
Extra info/examples/attachments
No response
The text was updated successfully, but these errors were encountered: