feat: Repacks (#23)
create(format): Repack CFs - Uses trash guides regexes as a baseline: https://trash-guides.info/Sonarr/sonarr-collection-of-custom-formats/#repackproper - Combines regexes into single patterns for performance - Explains different in p2p / scene naming standards tweak(profile): Add Repack CFs to quality profiles - Upgrade lone releases with repack / proper - Disregards freeleech by starting scores with +5
This commit is contained in:
parent
062f222108
commit
6ca6db355e
13 changed files with 425 additions and 0 deletions
30
custom_formats/Repack3.yml
Normal file
30
custom_formats/Repack3.yml
Normal file
|
|
@ -0,0 +1,30 @@
|
|||
name: Repack3
|
||||
description: 'Release groups use specific terms to indicate when they''re fixing issues
|
||||
in releases:
|
||||
|
||||
In Scene releases, groups can only occupy one release slot, which leads to two different
|
||||
terms:
|
||||
|
||||
- PROPER is used when a different group fixes issues in another group''s release
|
||||
|
||||
- REPACK is used when a group fixes issues in their own release
|
||||
|
||||
|
||||
P2P releases are simpler - REPACK is typically used whenever a group releases a
|
||||
fixed version.
|
||||
|
||||
|
||||
REAL / RERIP indicate similar things but their specific meaning / origin is unclear.
|
||||
|
||||
|
||||
This custom format will catch level 3 fixes'
|
||||
tags:
|
||||
- Flag
|
||||
- Repack
|
||||
conditions:
|
||||
- name: Repack3
|
||||
negate: false
|
||||
pattern: Repack3
|
||||
required: true
|
||||
type: release_title
|
||||
tests: []
|
||||
Loading…
Add table
Add a link
Reference in a new issue