Zugg Software :: View topic

Adept Joined: 04 Feb 2005 Posts: 246

CMUD is triggering on commands (normal pattern triggers, and not Command input triggers) just as if the zMUD preference "Trigger on Commands" was set. But that option is no longer around. This is a session I converted from zMUD, though that option wasn't set there either.

Any idea how to unset it?

Posted: Fri Jan 11, 2008 7:50 am

Are you saying that you have #ONINPUT triggers from zMUD that you want to keep, but CMUD thinks it's a pattern? If so, just change the type to say "Command Input" instead of "Pattern" in the box under the "Script Text" tab.

Charneus

Adept Joined: 04 Feb 2005 Posts: 246

No, I have normal Pattern triggers that CMUD is triggering on as if they were ONINPUT/Command Input triggers. In zMUD, there's a Trigger on Command preference that allows for this.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

Look at the %pref help. There were a lot of bad options like this in zMud that got removed from the preference pages in CMud.

Adept Joined: 04 Feb 2005 Posts: 246

Yup, #CALL %pref(TriggerCom, 0) did the trick. Thanks, I thought I remembered there was a way, just didn't remember what.

Posted: Fri Jan 11, 2008 6:36 pm

Hi Zhiroc, I was noticing a difference is just this when switching from Zmud to Cmud. I had to change some of my scripts because it was or wasn't detecting the same way in Zmud. Could you explain a little more of what this would affect?

Posted: Fri Jan 11, 2008 7:12 pm

Any trigger will execute on entered commands as if it were an oninput trigger if this option's enabled. If it's disabled, then pattern triggers will only run on text from the MUD.

Adept Joined: 04 Feb 2005 Posts: 246

Not entirely quite like an #ONINPUT trigger: you can't #GAG it (in zMUD), or #NOINPUT it (in CMUD). Nor can you #SUB on it to change it. You can react to it like any other text, as if it came from the MUD.