Zugg Software :: View topic

Newbie Joined: 02 Apr 2004 Posts: 4 Location: Canada

need help with this i am trtying to
Pattern: The random generator produces %1 out of %2 for %3.
#if (%3=@LEADER) {slot %1} {#wait 10}

It doesnt seem to be working any advice

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

A. Read the helpfiles for Pattern Matching
B. Include a more descriptive Topic Subject and include more details in your post :P
C. Read the helpfile for #wait as I have no idea why your doing the the #wait 10
Your trigger SHOULD be working though even with %1 though but try something like this
if it doesnt work post mud output and desc of what you are trying to do

#TR {^The random generator produces (*) out of (*) for (*).} {#if (%3=@LEADER) {slot %1} {#wait 10}}

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

%1-%99 aren't intended to be used as wildcards in trigger patterns. They can be replaced with * or other, more specific, wildcards. It appears that %1 and %2 would probably be numeric, so %d would likely be the best choice for them. Parentheses are used to create numbered parameters for use in the trigger value. Of your 3 wildcards, you don't use %2 so it doesn't need parentheses around it. That, of course, would change %3 to %2.

Zugg recommends that you DON'T use #WAIT in triggers. There's an article in the Support Library (link at top of page) which explains why. In this case, I don't see any reason to use #WAIT since you don't take any action after it. All it will do is suspend processing (ALL trigger processing) for 10 milliseconds. If there is a good reason to suspend THIS trigger, it can be accomplished with a multistate trigger using the Wait type.

#TR rg {The random generator produces (*) out of * for (*).} {#IF ("%2" = @LEADER) {slot %1;#STATE rg 0}}
#COND {} {} {Wait|Param=10}

Newbie Joined: 02 Apr 2004 Posts: 4 Location: Canada

Problem resloved thank you Lightbulb