Zugg Software :: View topic

Wanderer Joined: 02 Dec 2001 Posts: 80 Location: Canada

Im having trouble making it fire correctly
when I first set it up and added all the possible attack types supported by the mud I play eg {bludgeoned|missed|whatever} it worked ok. But if they did other commands like eat food or smoke a pipe etc it would also cause the trigger to fire disable the class until again we killed something (but that would cause me to reset the trigger states or assist in combat manually)

that was problem one... I thought I might be able to solve it by making all the possible attack or miss types into a variable and having the trigger look in there instead. I was wrong. It doesnt work at all now.
#trigger({@group}) *{(@attacks)}
assist %1
#t+ endjoin
#T- autojoin
or #trigger({@group}) *{@attacks}
assist %1
#t+ endjoin
#T- autojoin
dont work... is there a reason, am I missing something? maybe you know why the triggers were fireing on something that wasnt in string {blah|blah|blah}??
anyhelp would be greatly appreciated.

Wanderer Joined: 02 Dec 2001 Posts: 80 Location: Canada

another thing... zmud used to auto log me in.. ie chrname and password would be input, now it asks for chr name even though the session window says the name of ther chr, and once I put that in, it inputs the password? Only thing I did was create a new chr...
any suggestions?

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

Starting with the second question, check your login triggers. They are usually found in the Autolog class. It sounds like you probably have the wrong trigger phrases.

On the first question, use your Mud's auto-assist feature if it has one (most do). If not, there should be a space between #trigger and ({@group}). For command line entry, the entire trigger phrase needs to be surrounded by {} braces. Also, the parentheses are probably specific to the Mud the trigger was created for. There's no need for @attacks. You can use a stringlist directly the way the original triggers did, you don't need to put the list in a variable.

I'm assuming you're talking about the Autojoin triggers from the Sample Mud. For command line entry, they should look like this:

#TR {({@tank})*{annihilates|beats the shit|DEMOLISHES|SLAUGHTERS|cremates|tried to backstab}} {#t- autojoin;#t+ endjoin;@joincmd %1} {autojoin}

You can add as many additional "attack" phrases as you like to the list, just separate each one with a | vertical bar.

LightBulb
All scripts untested unless otherwise noted

Apprentice Joined: 18 Sep 2001 Posts: 175 Location: USA

Yeah I had that problem a couple of times where zmud would not auto-detect the char name trigger but would do the password.. So you take your mud's name entering trigger.. make a new trigger for it and make the command that it does
%char
And that should fix yer problem.. It did for me.

and Bulb is right, you gotta have a space after the #TRIGGER command :)

For tomarrow is another day, and other days come but 6 times a week.