Zugg Software :: View topic

Wanderer Joined: 27 Feb 2003 Posts: 69 Location: Australia

Anyone else encountering problems with reparse triggers when you output something from the trigger?

I have been doing some testing after encountering some problems, and have noticed that if I try to output anything from the trigger itself, the trigger just loops and hangs zmud.

Something like:
#TRIGGER {you say} {#SAY saying something!} <---output
#CONDITION {say} {#NOOP} "reparse"
#CONDITION {you} {#NOOP} "reparse"

just produces the output "saying something!" scrolling over and over and over when it triggers, and zmud stops responding.

So, am I doing something really silly?

Enchanter Joined: 20 Nov 2002 Posts: 627 Location: USA

this example has no meaing as far as i can tell
What is the reason for even having the conditions?

And triggers are still active when firing so if you have this:
trig {you say} {#say you say}
would probably trigger a loop

But check out the 'NOTRIG' option

Wanderer Joined: 27 Feb 2003 Posts: 69 Location: Australia

You're absolutely right. The example used as an illustration of the problem has no meaning whatsoever. But it is legitimate code as far as I can tell, which is what I'm asking.

If you want to know where it originated from, it's just the last trigger that I was using when testing this.

And no, there are no trigger loops over there, and there is no triggering going on. I checked for this. What I get is the same line of output again and again.

Thanks for your comments.

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

It would appear you've discovered a bug. Make a report and find another way of doing things until it's fixed.

WARNING: If you try this, you'll probably have to shutdown zMUD to stop it. You may have to reboot or even power off.

Wanderer Joined: 27 Feb 2003 Posts: 69 Location: Australia

Thanks for that, and sorry for the lack of warning. While I did say that zmud hangs, I should have spelled it out more clearly.

Beginner Joined: 23 Feb 2002 Posts: 23

I have had the same problem, when I was trying to echo something in the reparse trigger.