mudlet-makers team mailing list archive

[Heiko <koehnheiko@xxxxxxxxxxxxxx>]

You are correct. I really wonder how this one slipped in though as the 
code hasn't been intentionally changed for a very long time.
Must have been a slip on my part.
Fixed in current git. We'll need to update the mac version.

Iocun wrote:
> <pre wrap>Public bug reported:
>
> tempRegexTrigger() does never fire for me at all in Mudlet 1.0.5 on Mac
> (OS X 10.6.2). tempTrigger() seems to work fine.
>
> Example:
> gtrigger = tempRegexTrigger("level", [[echo("regex match")]])
> btrigger = tempTrigger("level", [[echo("trigger match")]])
>
> Mud sends line: "You are level 75 (Almighty) and 87.9% of the way to 
> the next level."
> -&gt; I get the echo "trigger match" (i.e. the tempTrigger fired), but 
> not "regex match" (i.e. the tempRegexTrigger didn't fire.)
>
> It used to work for me in 1.0.4.
>
> ** Affects: mudlet
>      Importance: Undecided
>          Status: New
>
> </pre></body>
> </html>
> </html>

-- 
tempRegexTrigger() doesn't fire
https://bugs.launchpad.net/bugs/502007
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.

Status in Mudlet the MUD client: New

Bug description:
tempRegexTrigger() does never fire for me at all in Mudlet 1.0.5 on Mac (OS X 10.6.2). tempTrigger() seems to work fine.

Example:
gtrigger = tempRegexTrigger("level", [[echo("regex match")]])
btrigger = tempTrigger("level", [[echo("trigger match")]])

Mud sends line: "You are level 75 (Almighty) and 87.9% of the way to the next level."
-> I get the echo "trigger match" (i.e. the tempTrigger fired), but not "regex match" (i.e. the tempRegexTrigger didn't fire.)

It used to work for me in 1.0.4.