Zugg Software :: View topic

Wanderer Joined: 29 Sep 2001 Posts: 75 Location: Israel

Do #oninput triggers being processed when the option "Trigger on command line" in settings set off?
And if no, how can I fix it, besides turning this option off?

Thank you,

- Amfitrion.

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

quote:

Do #oninput triggers being processed when the option "Trigger on command line" in settings set off?
And if no, how can I fix it, besides turning this option off?

Thank you,

- Amfitrion.

#ONINPUT fires only on command-line text sent to the screen (as in #SAY, #ECHO, or #SHOW) or to the MUD (as in any game command). If this ability is disabled, then #ONINPUT is worthless.

If you don't want to have triggers firing off your commands via the command-line, you need to convert the #ONINPUT trigger into a #TRIGGER trigger (pattern-style). This trigger will fire on any occurrance of the pattern no matter where it came from.

li'l shmoe of Dragon's Gate MUD

Wanderer Joined: 19 Jul 2001 Posts: 59 Location: Germany

I tried (in an empty mud window):
#TRIG {aaa} {#ADD test trig}
#ONINPUT {aa} {#ADD test oninp}
test=""
#STATUS @test

when I now type
#SH aaaa
the normal (#TRIG) trigger fires, but not the #ONINPUT trigger - regardless of the settings for 'trigger on commands'.
While typing
aaaaa
makes both triggers fire IF 'trigger on commands' is enabled, while only the #ONINP trigger fires if the option is disabled.

Summary - the 'trigger on commands' option doesn't affect #ONINPUT triggers at all, it's only for 'normal' triggers.
(Lots of text just to express the everything works as expected.)