Flood: Regex download rules

Created on 14 Aug 2017  路  11Comments  路  Source: Flood-UI/flood

I can't get this to work.

.*Video.*1080p.*should in theory download all torrents from an RSS feed that contain both those patterns, correct?

question

All 11 comments

Maybe the order is the issue? This regex will match only if Video and 1080p are both present _and_ in that order.

The order is the issue.

It will only match names as such (in this order, first "Video", then "1080p":
Some.Show.Name.HDTV._Video_.Something.Here._1080p_.x264-FLOOD

and no other torrents.

It will _not_ match
Some.Show.Name.HDTV._1080p_.Something.Here._Video_.x264-FLOOD

Test your regex here http://regexr.com/

Try this: (Video|1080p)

This should match any title with either of those in any order.

OP, please clarify what you want, matches including both or 'either or'.

@randomnonsense and @SanPilot are correct and deserve a _huge_ "thank you" for answering this! 鉂わ笍

I'm coming from ruTorrent and I've been trying for the last 3 hours to wrap my head around how the RSS works in Flood.

This is a regex example from ruTorrent:
/Name of Series.*(s|S)(2|02)(e|E)?[0-30]+.*(720p|1080p).*/i

It will match:
Name of Series
Season 2
Episode 0 to 30
720p or 1080p
It will be case-insensitive (/i)

So how is Flood doing it? Can I not use the RSS regex straight off from ruTorrent? Any help is greatly appreciated. ping @SanPilot @randomnonsense @jfurrow Thanks!

This pattern should work:
Name of Series.*(s|S)(2|02)(e|E)?[0-30]+.*(720p|1080p).*

I believe it is case-insensitive by default.

@SanPilot is right, RegExp(rule.match, 'gi') g is for global and i for case insensitive.

Guys, you are awesome! Just changed my feeds.db to match your suggestions. Let's hope it works!

Yup, it worked, just awesome!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

noeuse picture noeuse  路  5Comments

NoLooseEnds picture NoLooseEnds  路  6Comments

Phr33d0m picture Phr33d0m  路  6Comments

noraj picture noraj  路  3Comments

NoLooseEnds picture NoLooseEnds  路  3Comments