Zugg Software :: View topic

Newbie Joined: 14 Jul 2003 Posts: 5

Ok Ive written a class that assigns each member of a group to a variable the group statement looks like this...

Your group consists of:
( Head) 731/983 hit, 176/176 move Char1
(Back ) 868/868 hit, 115/115 move Char2
(Front) 1324/1324 hit, 259/259 move Char3

here are my triggers

#CLASS {group setter}
#CLASS {group setter on}
#TRIGGER {^* %d/%d*hit,* %d/%d move (%w)} {#add cntr (1);#var group@cntr %1;#say group@cntr set to %1} "group setter"
#TRIGGER {< %dh/%dH} {#var cntr 0;#t- {group setter on};#t- {group setter}} "group setter"
#TRIGGER {Your group consists of:} {#t+ {group setter}} "group setter on"

I have the trigger put up a say so I can see that it was properly done. When I type gset it turns on the group setter on class and the output is like this...

Your group consists of:
( Head) 731/983 hit, 176/176 move Char1
group1 set to Char1
(Back ) 868/868 hit, 115/115 move Char2
group2 set to Char2
(Front) 1324/1324 hit, 259/259 move Char3
group3 set to Char3

Anyway it works great, but... If the players move points are below 100 the are not added. So what is wrong with my pattern?

Any ideas?

I also have questions regarding the #t command if I have a class folder beneath another what is the syntax to disable the class beneath? Like above I have group setter on and group setter classes, could I put group setter class under group setter on class, deactivate the group setter class without deactivating the group setter on class?

SubAdmin Joined: 18 Nov 2001 Posts: 5182

When deactivating a class all subclasses are also deactivated. The reverse is not true.

As to not triggering on move<100 it would seem your mud is formatting the text with spaces, try using the %s wildcard so the pattern would be: {^%s%d/%d%****,%s%d/%d%smove (%w)