Zugg Software :: View topic - [1.30] #ONINPUT makes triggers "notrig" by default

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

I used the following test code to figure out why my events weren't firing, and I narrowed it down to the command input triggers being created with "trigger on trigger" off by default. If I open my Package Editor and check the box, the event suddenly starts working as intended. Since there is no explicit option to turn "trigger on trigger" ON with a trigger, only OFF, I thought it important to mention the problem.

Posted: Thu Apr 26, 2007 10:04 pm

Yes, this is done on purpose to prevent nasty trigger loops in oninput triggers. Normally you wouldn't want to trigger on the results of OnInput since the result is supposed to be sent to the MUD as a command, and not to the screen.

In any case, I'll see about adding a way to turn the option on in the command line definition.

Actually, looking at your example...is it just the Event that doesn't get triggered? I should probably change it so that you can still raise events, even if Trigger on Trigger is turned off.

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

The command input trigger fires when I do "tevt" to test it, but it doesn't raise the event because of the trigger on trigger option, it seems. It should be safe to allow triggers to raise events independently of the trigger on trigger option. Events are just triggers, right? So, I can understand that this is a sort of side effect going on.

Either way this goes for the fix, thanks in advance!