 |
chamenas
Wizard
Joined: 26 Mar 2008
Posts: 1547
|
 Posted: Thu Apr 03, 2008 8:39 am
Broken
|
My auto quit trigger has broken again, for some reason.
| Code: |
#TRIGGER auto_quit {@void_count>=5} {quit;#disconnect} {General Triggers} {exp}
|
Worked fine for awhile, and I haven't changed a thing except other, unrelated triggers and now it won't fire.  |
|
|
|
|
Larkin
Wizard
Joined: 25 Mar 2003
Posts: 1113
Location: USA
|
Posted: Thu Apr 03, 2008 11:32 am
|
Not sure if it's still true, but I always had to put the expression itself in parentheses rather than curly brackets for an expression trigger to fire correctly.
|
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Thu Apr 03, 2008 11:32 am
|
Create an alias in the same class that does #show @void_count to see if the trigger is aware of the variable. You could also put @void_count in the body of the trigger and then double-click it to be taken to the variable that the trigger is using (if it can find one). The most likely culprit is that you've accidentally made another void_count variable so the trigger isn't seeing the one that's being updated, or that something's become disabled that's stopping either the trigger from firing or the variable from being seen.
|
|
|
|
|
chamenas
Wizard
Joined: 26 Mar 2008
Posts: 1547
|
Posted: Thu Apr 03, 2008 12:02 pm
|
I already have that. I even have one to increase the account. IT goes up past the number and won't work. The frustrating part is that it DID work, and now, for no apparent reason, it doesn't.
|
|
|
|
|
chamenas
Wizard
Joined: 26 Mar 2008
Posts: 1547
|
Posted: Fri Apr 04, 2008 2:33 am
|
Can no one else tell me why it's broken? None of the suggestions are true. No new variables, etc...
|
|
|
|
|
charneus
Wizard
Joined: 19 Jun 2005
Posts: 1876
Location: California
|
Posted: Fri Apr 04, 2008 12:08 pm
|
Weird. I thought I posted a reply to this, but apparently it didn't go through. Anyway...
Have you deleted the trigger and recreated it to see if the problem continues? Has your trigger been inadvertently changed to a different scripting language (i.e. Lua, Perl, VBScript)? Have you tried disabling all folders minus this group to see if that fixes the problem? A daunting task, I know, but still... it's how I found out where my bugs were.
Personally, I wasn't aware you could use a conditional statement as a trigger. I always thought it had to fire off a line from the MUD output screen. If I'd know this, I probably would have done a few more triggers. ;)
Charneus |
|
|
|
|
chamenas
Wizard
Joined: 26 Mar 2008
Posts: 1547
|
Posted: Fri Apr 04, 2008 12:42 pm
|
Fang was the one that told me I could, and it has worked. So yes. I guess I can try those things.
|
|
|
|
|
|
|
|
