rssResults = [
{name: some_name1, quality: some_quality, language: some_language, indexer: some_indexer1, points: 10},
{name: some_name1, quality: some_quality, language: some_language, indexer: some_indexer2, points: 10},
{name: some_name2, quality: some_quality, language: some_language, indexer: some_indexer1, points: 10},
{name: some_name2, quality: some_quality, language: some_language, indexer: some_indexer2, points: 10},
{name: some_name2, quality: some_quality, language: some_language, indexer: some_indexer3, points: 20},
]
Lets assume some_name1 is a tie for points, quality (both are 720), language (both are english), etc and this is where the indexer priority would come into play. It could/should be the last thing checked when there are multiple results for the same file with the same compare outcome. If there is a result such as some_name2 that has a higher score from an indexer that isn’t the priorty it would still grab that one because the other factors put it higher.
I guess in my head this would work as the indexer priority only comes into play if the release is a “tie” as far as all the other factors are concerned.
Sonic.The.Hedgehog.2020.1080p.WEB-DL.H264.AC3-EVO
is found on 5 indexers and show up in the rss for each one, so it is in there 5 times? or does it not do it that way and only adds 1 release to the stack per name even if it is found on multiple indexers? If it is in there 5 times, then this logic should work. After the compare balancing act is done and it determines the score for the release it then looks to see which of the indexers has it and pulls from the highest preferred one first.
Maybe i just cant put my thoughts to words well enough… i dunno