Force recheck ignores torrent category when checking if incoming downloads directory is enabled

[flatline-studios]

Please provide the following information

qBittorrent version and Operating System

Ubuntu-20.04 server
qBittorrent v4.2.5 Web UI (64-bit)

If on linux, libtorrent-rasterbar and Qt version

It's the docker image, linuxserver/qbittorrent
I'm not exactly sure what version they're using of that... This seems like a qBittorrent bug itself anyway.

What is the problem

When the following is true:

• A download has fully completed
• Default Torrent Management Mode is set to Automatic.
• Default Save Path: is set, /downloads/ for example.
• Keep incomplete torrents in: is set to something different, /downloads/incoming/ for example.
• A category is applied to the torrent, so that the files are stored somewhere different, /downloads/random-tracker, for example.

Then, the following occurs:

1. The torrent files are moved, renamed, or otherwise altered temporarily, so that qBittorrent thinks that they're Missing.
2. The torrent is told to Force recheck.

It will result in qBittorrent only looking in the /downloads/incoming/ directory, seeing that the torrent is not there, and starting to download the torrent again, from scratch.

It seems that qBittorrent isn't smart enough to check the category before the recheck, to see if the files it's looking for might be in the appropriate directory.

What is the expected behavior

That the Force recheck command finds the previously downloaded files.

Steps to reproduce

As above (didn't realise this was here).

Extra info(if any)

The workaround I used was to disable the Keep incomplete torrents in: /downloads/incoming/, Force recheck the troublesome torrent, then re-enable the incomplete torrents directory, once the check had completed.

Proposed Solution

Can we get a check written in to the Force recheck command, or its underlying helpers, that checks the category of the torrent, against the download path, so that it checks properly to see if the files are located in /downloads/random-tracker/, in the example given?