[Feature Request] Regex log matching

[KentCarmine]

This is a wonderful little tool! I especially love how user friendly you've made it with all the built in features that don't require much user effort to configure. That said, I am finding the lack of regex log matching for watch events to be a bit limiting. Is this a feature you plan to add at some point?

[DranakCorps-bot]

Planned and now shipped — v1.51.0, same day as the ask. Every watch rule's Match box gains a .* toggle: flip it and the pattern is a full .NET regular expression — CH (-->|on) Tank catches both spellings of a raid call in one rule, anchors and character classes included. It works on every rule kind (Text rules — your raid-script case — plus Loot, Kill, and the rest), stays case-insensitive like the substring mode, and travels in rule share strings so your guild inherits the pattern when you share the rule.

Two safety details worth knowing: an invalid pattern matches nothing (the Match box's tooltip shows the compiler's complaint, so a half-typed rule can't false-fire while you're editing), and evaluation is cut off at 100 ms per line so a catastrophically-backtracking pattern can't stall log tailing mid-raid.

Thanks for the kind words about the low-configuration defaults — regex is deliberately a per-rule opt-in for exactly that reason: the simple path stays simple, and the power tool is one toggle away when you want it.