Noah Petherbridge

Both forms seem to work for me on v1.14.4: First: ``` . . .:...:: RiveScript Interpreter (Python) .:: ::. Library Version: v1.14.4 ..:;;. ' .;;:.. . ''' . Type '/quit'...

Can you test with the version on pip and a simplified test file that only tests the code snippet given on this ticket? The versions of the module on pip...

Possible problematic cases: In `_reply_regexp` near line 2299 when handling optionals in triggers: ``` python regexp = re.sub(r'\s*\[' + re.escape(match) + '\]\s*', '(?:' + pipes + r'|(?:\\s|\\b))', regexp) ``` If...

Yeah, using parenthesis inside of `! array` values isn't supported behavior. RiveScript is heavily powered by regular expressions under the hood, but the user-facing language uses "simplified regular expressions" for...

Hey @johnnymast The shortcut tags like `, , ` and `` only translate to affecting the `` tag, for the very niche use cases of simple triggers like: ``` +...

Something like this might work: https://play.rivescript.com/s/ss8WgUpO4p ``` ! version = 2.0 // Wildcard replies normally under normal conditions but // will reply `no-match` when the uservar `testing=true` + * *...

What's the use case for the topic callback? Under the hood, topics are just user variables (e.g. `` would do the same as `{topic=random}`, except the `{}` syntax has priority...

Something like this maybe: ``` + alfred *{weight=100} - + * alfred{weight=100} - ``` The high weight value should ensure the trigger gets tested _first_ (unless you have other triggers...

Yeah I was aware of the Unicode punctuation getting in the way of that, but I just thought of a way I might work around it: > Don't remove punctuation...

It's not officially supported, but you could use an object macro and parse the message yourself. Before calling `.Reply()`, store the user's original message in a user variable and then...