starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Allow to select share limit as AND / OR #9849

New issue

Open

opened 2026-02-21 20:25:06 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-21 20:25:06 -05:00

Owner

Originally created by @navara on GitHub (Mar 6, 2020).

I would like to choose if either one or both of the limits has to be reached to stop seeding of the torrent.

Now: QB stops seeding when either of the limits ( ratio / minutes ) is achieved.
Future: Checkbox that will require both limits to be achieved to stop seeding of the torrent.

Why: I would like to share until ratio 2.0 is achieved and at least for two days. Even if ratio reaches 10.0 in those two days or it takes two weeks to achieve ratio of 2.0.

qBittorrent version and Operating System

Windows 10, QB 4.2.1 64bit

Originally created by @navara on GitHub (Mar 6, 2020). I would like to choose if either one or both of the limits has to be reached to stop seeding of the torrent. **Now**: QB stops seeding when either of the limits ( ratio / minutes ) is achieved. **Future**: Checkbox that will require both limits to be achieved to stop seeding of the torrent. **Why**: I would like to share until ratio 2.0 is achieved and at least for two days. Even if ratio reaches 10.0 in those two days or it takes two weeks to achieve ratio of 2.0. ![image](https://user-images.githubusercontent.com/5062312/76085110-adec0e00-5fb1-11ea-87ca-a7cca4310ac3.png) ### qBittorrent version and Operating System Windows 10, QB 4.2.1 64bit

deekerman added the

Feature request

label

2026-02-21 20:25:06 -05:00

deekerman commented

2026-02-21 20:25:08 -05:00

Author

Owner

@mbs commented on GitHub (Feb 19, 2022):

If it's decided to keep this function as-is, I suggest add the text 'or' to the dialog box, to clarify the function. I would personally enjoy both the choice of 'and/or' in the global and per-torrent seed options, and also the 'Then [choice of action]' per-torrent instead of just globally. Ideally I want to be able to set a policy applying only to a seed category, so those get seeded until the conditions are met, then deleted.

@mbs commented on GitHub (Feb 19, 2022): If it's decided to keep this function as-is, I suggest add the text 'or' to the dialog box, to clarify the function. I would personally enjoy both the choice of 'and/or' in the global and per-torrent seed options, and also the 'Then [choice of action]' per-torrent instead of just globally. Ideally I want to be able to set a policy applying only to a seed category, so those get seeded until the conditions are met, then deleted.

deekerman commented

2026-02-21 20:25:11 -05:00

Author

Owner

@TheIronAngel commented on GitHub (Apr 22, 2022):

I second this, couldn't find it when I searched, that would be one of the few things that would make this a perfect switch from uT for me.

@TheIronAngel commented on GitHub (Apr 22, 2022): I second this, couldn't find it when I searched, that would be one of the few things that would make this a perfect switch from uT for me.

deekerman commented

2026-02-21 20:25:11 -05:00

Author

Owner

@antanilol commented on GitHub (Feb 10, 2024):

This would be super nice to have, especially now that we have the inactive seeding time option

@antanilol commented on GitHub (Feb 10, 2024): This would be super nice to have, especially now that we have the inactive seeding time option

deekerman commented

2026-02-21 20:25:11 -05:00

Author

Owner

@Batorian commented on GitHub (Apr 17, 2025):

I'd like to second this. My torrent just got removed after downloading because it had a ratio over 1.5. It got removed so fast the file couldn't even get imported. Meaning I downloaded the file only to have it instantly removed.

@Batorian commented on GitHub (Apr 17, 2025): I'd like to second this. My torrent just got removed after downloading because it had a ratio over 1.5. It got removed so fast the file couldn't even get imported. Meaning I downloaded the file only to have it instantly removed.

deekerman commented

2026-02-21 20:25:11 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 24, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 24, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**

Rows
Columns