mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Custom Limit Share Ratio per Category #11355
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#11355
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Dec 3, 2020).
Please provide the following information
qBittorrent version and Operating System
latest/windows
If on linux, libtorrent-rasterbar and Qt version
n/a
What is the problem
Would be useful to have the option to set the "Limit Share Ratio" option per category, same as we can set different save directories depending on the category.
Examples:
Category label X has a Limit Share Ratio of 2
Category label Y has a Limit Share Ratio of 0
What is the expected behavior
Be able to set different share ratio limits depending on the category of the torrent.
Would need t think on what takes priority on torrents in multiple categories with different values; perhaps use the higher custom share ratio.
Steps to reproduce
n/a
Extra info(if any)
n/a
@sakej commented on GitHub (Apr 16, 2022):
+1
@thalieht commented on GitHub (Feb 13, 2024):
Duplicate of #590