Zugg Software :: View topic - Autoheal trigger won't fire.....sometimes?

Novice Joined: 22 Jun 2009 Posts: 38

I have an autohealer that won't fire. That is, 1% of the time it doesn't fire. the trigger pattern is an expression, and it's simple:

Sorcerer Joined: 13 Jan 2006 Posts: 715

I don't believe thats a valid trigger pattern... but I've not really programmed on CMUD much so I could be wrong.

However, you obviously have some kinda trigger that scans your prompt to set the curhp variable, right?

So, in THAT trigger after the variable is set, just CHECK IT and make it call a heal alias or place all the heal code there. By check it, I mean put:

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

It's a valid pattern. He's using an expression trigger, which looks a little like this:

#trigger "tHealHealth" (@curhp / 1400) {whatever it does here}

A pattern trigger, on the other hand, looks like this:

#trigger tHealHealth" {Dude, your leg just fell off and you're gushing blood!} {whatever it does here}

Sorcerer Joined: 13 Jan 2006 Posts: 715

Gotcha, something new in CMUD I take it? I really should get up to date on CMUD programming.

Still, my idea should work for him, instead of making a whole second trigger for it.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Nope, it's at least as old as the current state model, which was originally installed I believe in the late 6.xx ZMud days. That was a good 6 or 7 years ago or so.

To get back on topic, though, if no classes are being enabled/disabled or some other form of scope change, it's probably an old bug that was long since fixed (either fixed-fixed, or "I got frustrated and rewrote the whole thing"-fixed) as part of the current beta cycle. CMud 2.37 is now approaching ZMud-like territory in how comparatively old it is, so it's getting rather hard to keep track of what's been fixed and what's still bugged in 2.37.

Sorcerer Joined: 13 Jan 2006 Posts: 715

Ok, I guess I just never used that functionality in zMUD, I've always done things the way I suggested he do them. LOL

Thanks Matt, always good to learn something new.

Novice Joined: 22 Jun 2009 Posts: 38

I should have mentioned. I'm using #setprompt to capture my prompt. I tried using a trigger for about 6 weeks, and couldn't get it to work as well as #setprompt. Basically the same thing is happening with my expression trigger, though. Every time the variable (in this case, @curhp) changes, this expression is checked. it seems like it's not firing for a small period of time, though, so i just don't get it. What should i do? Should i just erase this one and rewrite it in the same way?

Edit: I also asked for cmud support because i feel like it's a bug, and they of course referred me to the forums.