This is a known problem with the alpha and beta build (for example here http://forums.mudlet.org/viewtopic.php? ... =10#p21774 or multiple comments after that). But the devs are working on it

Not for a while now, but I seldomly created new profiles in the meantime.

It does answer... Read feteaera's and my answer again...

not matches[4] == "Scent equals (not matches[4]) == "Scent" which is false == "Scent"

ETA: and "~=" is usually the easier understood version of "not equal" anyways....

Also remember "scent" and "Scent" are different things.

the second version can be translated as

if (not matches[4]) == "Scent" then

which probably not what you want. Version 1 is the correct one, though you could write it as

if not (matches[4]=="Scent") then

as well.

Ah. I missed that crit was actually a modifier... Yay for reading comprehension

Vadi wrote:What I do is have my modules raise an event when they are loaded, and make anything that uses them load off that event.

Question to this approach: What happens if the module that is used finishes loading, before the using part gets a chance to register the callback?

I'd do something like this: local pattern = rex.new("^(left|right)?(arm|leg|torso|head)(modbruised|bruised|crit|broken)$") local side, limb, aff = pattern:match(nextSmash[1]) local hitlimb = (side and (side .. " ") or "") .. limb --[[ Now the variables contain: aff - th...

Try someting like this: http://forums.mudlet.org/viewtopic.php?f=9&t=4432

Upon further analysis of your code we have a quite similar approach, although mine seems to be a bit less hardcoded. I uploaded my current work in progress to github into https://github.com/keneanung/MudletPackageManager/tree/cleanup which contains some bugfixes but primarily localizing and creation...