Add torrent dialog: let users add torrents in Forced state #9460

New issue

Open

opened 2026-02-21 20:11:42 -05:00 by deekerman · 2 comments

deekerman commented

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

Owner

Originally created by @Balls0fSteel on GitHub (Dec 13, 2019).

This is like a super simple request/idea. Hopefully, not a duplicate.
Basically, it would be great if there was a checkbox in the add torrent dialog for making the new torrent have a "Forced" state. Honestly, a new button near OK would make the perfect sense - but if users have no clue what "Forced" means, the option to add a torrent forced should not be so visible.

Why / Reasoning: I have my client limited to 0.00 ratio as I don't want to seed things that I already seed elsewhere or things that have super great swarms (like Ubuntu). So whenever I add a torrent that I do actively want to seed, I add it, then right-click, "Force Resume". This works superb. But if I forget to do this, I can catch a hit and run or end up not seeding.

Just a little bit of convenience. Thank you.
Feel free to close the ticket if you see no point in adding it!

Originally created by @Balls0fSteel on GitHub (Dec 13, 2019). This is like a super simple request/idea. Hopefully, not a duplicate. Basically, it would be great if there was a checkbox in the add torrent dialog for making the new torrent have a "Forced" state. Honestly, a new button near OK would make the perfect sense - but if users have no clue what "Forced" means, the option to add a torrent forced should not be so visible. Why / Reasoning: I have my client limited to 0.00 ratio as I don't want to seed things that I already seed elsewhere or things that have super great swarms (like Ubuntu). So whenever I add a torrent that I do actively want to seed, I add it, then right-click, "Force Resume". This works superb. But if I forget to do this, I can catch a hit and run or end up not seeding. Just a little bit of convenience. Thank you. **Feel free to close the ticket if you see no point in adding it!**

deekerman added the

Feature request

GUI

labels

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

deekerman commented

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

Author

Owner

@Medvedishce commented on GitHub (Dec 15, 2019):

I suggest to add both options and make Feature requests to be linked because both make prioritization in two different ways and it preferable to have both variants:

Add torrent to top priority option #357, Superseded by #11599
Add torrents in Forced state #11659

@Medvedishce commented on GitHub (Dec 15, 2019): I suggest to add both options and make Feature requests to be linked because both make prioritization in two different ways and it preferable to have both variants: - Add torrent to top priority option #357, Superseded by #11599 - Add torrents in Forced state #11659

deekerman commented

2026-02-21 20:11:45 -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.)**