mudlet-makers team mailing list archive

[Iocun <j-weg@xxxxxxx>]

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."
-> 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

-- 
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.