Zugg Software :: View topic

Newbie Joined: 04 May 2006 Posts: 5

Seems to have ported all triggers from zMud without issue, however I can't seem to get any of them to work. They are "enabled" but still do not execute ...

Newbie Joined: 12 Jun 2006 Posts: 3

i have had the same problem, i ended up remaking some of mine, they looked idenical but they seemed to work after that....well some of them anyways

Posted: Mon Jun 12, 2006 6:28 pm

yup. loaded old settings, nothing works, even simple colouring triggers. started poking around the new weird interface, boom
EDatabaseError
MemCursor: Cannot perform this opeartion on a closed dataset.
well what did you expect, its a beta 1.0 Very Happy

Posted: Mon Jun 12, 2006 6:51 pm

One thing I've seen is that when you first import a MUD file, some things don't seem to work. Exit CMUD and then reload it to get the new *.pkg package version of your settings. Then they seem to work. Also, triggers entered on the command line work.

So, I think it's an issue with the .MUD importing rather than with the triggers themselves.

Beginner Joined: 11 Jun 2006 Posts: 20

I can't get brand new triggers working.

I made an alias K, to do dance

Then when I see the word "north" I should do K

I never dance when I see the north exit.

This is being done on the Aetolia mud.

(i.e. I click on the pregiven Aetolia icon and enter that way)

Posted: Mon Jun 12, 2006 7:08 pm

As I said, exit CMUD and restart it and see if that helps. Here is what I just entered that worked fine for me:

Beginner Joined: 11 Jun 2006 Posts: 20

I'm not loading any .mud files.

Its a brand new clean slate, and I have restarted the program 3 times.

What I have seen, is that if you make the triggers in the command line, it works fine, but if you make the new triggers in the GUI it doesn't work at all. Sometimes, when I reload the .pkg files, the trigger is blank.

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

I see similar oddities. Settings made on the command line seem to work well. Ones made in the editor are hit-and-miss.

Here's what I just did:

1. Opened CMUD and hit ESC to get a blank session.
2. Command-line alias and trigger, #ALIAS blah {#say Test one.};#TRIGGER {one} {#show Passed}
3. Output was what I expected when I did "blah" from the command line. "Test one." followed by "Passed" on the next line.

Completely closed CMUD, and then:

1. Another blank session.
2. Opened the settings editor.
3. New alias "blah" with command "#say Test one." and save changes.
4. New trigger "one" with the command "#show Passed" and save changes.
5. Close the settings editor.
6. Entering "blah" on the command line showed me the "Test one." and did not follow with "Passed" this time.

I have seen some aliases and triggers work from the settings editor and others not. Can't find a rhyme or reason yet as to which ones work or why others don't.

Magician Joined: 29 Nov 2005 Posts: 482

How about ONINPUT mine isnt working..

#ONINPUT {^(%t)$} {#VARIABLE lastDir %1} "" {notrig}

Firstly i had to change it to
#ONINPUT {^(%t)$} {#VARIABLE lastDir %1} {MMSYSTEM} {notrig} to get past the syntax editor however its still not setting the variable when i move