-
-
Notifications
You must be signed in to change notification settings - Fork 246
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Created new Custom Format Scoring info includes for Radarr and Sonarr
- Added new Custom Format Scoring info includes to info sections for Radarr and Sonarr
- Loading branch information
Showing
4 changed files
with
54 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
23 changes: 23 additions & 0 deletions
23
includes/radarr/custom-format-basic-scoring-information.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
<!-- markdownlint-disable MD041--> | ||
!!! info "How Does Custom Format Scoring Work?" | ||
|
||
Let’s say you have three custom formats, A, B and C. Scored as: | ||
|
||
A: 10 | ||
B: 20 | ||
C: 30 | ||
|
||
Then, let’s say you have three releases, X, Y and Z. They happen to match your custom formats as follows: | ||
|
||
X matches A | ||
Y matches B and C | ||
Z matches A and C | ||
|
||
Total custom format scores would therefore be: | ||
|
||
X: 10 (matches A) | ||
Y: 50 (matches B and C) | ||
Z: 40 (matches A and C) | ||
|
||
Quality is the first check. If all three of our example releases here are the same quality - eg, WEBDL-1080p, then we move on to the next check which is custom format score. In the example above, Y would be chosen as it has the highest cumulative custom format score. | ||
<!-- markdownlint-enable MD041--> |
23 changes: 23 additions & 0 deletions
23
includes/sonarr/custom-format-basic-scoring-information.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
<!-- markdownlint-disable MD041--> | ||
!!! info "How Does Custom Format Scoring Work?" | ||
|
||
Let’s say you have three custom formats, A, B and C. Scored as: | ||
|
||
A: 10 | ||
B: 20 | ||
C: 30 | ||
|
||
Then, let’s say you have three releases, X, Y and Z. They happen to match your custom formats as follows: | ||
|
||
X matches A | ||
Y matches B and C | ||
Z matches A and C | ||
|
||
Total custom format scores would therefore be: | ||
|
||
X: 10 (matches A) | ||
Y: 50 (matches B and C) | ||
Z: 40 (matches A and C) | ||
|
||
Quality is the first check. If all three of our example releases here are the same quality - eg, WEBDL-1080p, then we move on to the next check which is custom format score. In the example above, Y would be chosen as it has the highest cumulative custom format score. | ||
<!-- markdownlint-enable MD041--> |