From 8b173661038c9c2bc82f13b725cac7a9f2b93d9f Mon Sep 17 00:00:00 2001 From: ben-ba Date: Wed, 18 Aug 2021 03:15:26 +0200 Subject: [PATCH] seeding_time_limit vs max_seeding_time explanation --- WebUI-API-(qBittorrent-4.1).md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/WebUI-API-(qBittorrent-4.1).md b/WebUI-API-(qBittorrent-4.1).md index a32c82a..846319b 100644 --- a/WebUI-API-(qBittorrent-4.1).md +++ b/WebUI-API-(qBittorrent-4.1).md @@ -1297,7 +1297,7 @@ Property | Type | Description `ratio_limit` | float | TODO (what is different from `max_ratio`?) `save_path` | string | Path where this torrent's data is stored `seeding_time` | integer | Torrent elapsed time while complete (seconds) -`seeding_time_limit` | integer | TODO (what is different from `max_seeding_time`?) +`seeding_time_limit` | integer | TODO (what is different from `max_seeding_time`?) seeding_time_limit is a per torrent setting, when Automatic Torrent Management is disabled, furthermore then max_seeding_time is set to seeding_time_limit for this torrent. If Automatic Torrent Management is enabled, the value is -2. And if max_seeding_time is unset it have a default value -1. `seen_complete` | integer | Time (Unix Epoch) when this torrent was last seen complete `seq_dl` | bool | True if sequential download is enabled `size` | integer | Total size (bytes) of files selected for download