Zugg Software :: View topic

Beginner Joined: 15 Feb 2001 Posts: 20 Location: USA

I have a trigger for whenever someone stands up..

ie: A drow clambers to his feet

I used as the trigger: (%w) clambers to

but for the output, what do i use so it conveys WHOM is standing up..

i just get an echo that has a blank space and then says clambers to his feet..

Beginner Joined: 15 Feb 2001 Posts: 20 Location: USA

other issue , i guess about classes,
i use my numerical keypad as a direction key..
i need help in setting up, i suppose would be a class that is easy to engage and disengage, so that when actively trying to PK a particular target , my keypad not only has direction keys but my target alias KK in it
command would be:
NE
KK

or
SE
KK

make sense?

Beginner Joined: 15 Feb 2001 Posts: 20 Location: USA

I guess while i'm at it with my christmass list..

what would be the verbage to take this mud input:
An Ogre attacks Leodo. [5 hits]

into an echo that will place the attackee into a echo that says:
-=-=-=-= Now Tanking: Leodo

Beginner Joined: 19 May 2002 Posts: 15

umm try this
Trigger: (*) clambers to

Then statement:
#SA %1 has stood up

i forget the command line syntax for a trigger, isn't that terrible!

The numeric keypad thing, i dunno, never played with it, and for you last one, pretty easy

Trigger: attacks (%w).
statement: @tank = %1;#sa now tanking @tank

depending on mud output tho, this could change to be the mob...ie.
Leodo attacks An Ogre. [5 hits]

in which case "an" would become the tank...all depends on the verbage really

Beginner Joined: 19 May 2002 Posts: 15

and actually on the last one, you could skip the variable completely if you wanted it to just put output every round

Trigger: attacks (%w).
statement: #sa Now Tanking %1

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

Use %1.

Create a class to hold the new macros. I'd recommend making it disabled at connection.
#CLASS KeypadPK disable
Now, copy all the current macros from the classes System|Keypad and System|KeypadDiag to KeypadPK. Edit each macro to add the KK command.
Use an alias, button, or other method of your choice to switch between the normal and PK versions by disabling the normal classes and enabling the PK class or vice-versa.
#AL pk {#T- System|Keypad;#T- System|KeypadDiag;#T+ KeypadPK}
#AL nopk {#T- KeypadPK;#T+ System|Keypad;#T+ System|KeypadDiag}

#SUB {* attacks (%w) ~[%d hits~]} {~-~=~-~=~-~=~-~= Now Tanking: %1}

Can't say that I see any benefit to rewording the MUD output, but that's how you do it.

LightBulb
Senior Member

Beginner Joined: 15 Feb 2001 Posts: 20 Location: USA

quote:

Use %1.

Create a class to hold the new macros. I'd recommend making it disabled at connection.
#CLASS KeypadPK disable
Now, copy all the current macros from the classes System|Keypad and System|KeypadDiag to KeypadPK. Edit each macro to add the KK command.
Use an alias, button, or other method of your choice to switch between the normal and PK versions by disabling the normal classes and enabling the PK class or vice-versa.
#AL pk {#T- System|Keypad;#T- System|KeypadDiag;#T+ KeypadPK}
#AL nopk {#T- KeypadPK;#T+ System|Keypad;#T+ System|KeypadDiag}

#SUB {* attacks (%w) ~[%d hits~]} {~-~=~-~=~-~=~-~= Now Tanking: %1}

Can't say that I see any benefit to rewording the MUD output, but that's how you do it.

LightBulb
Senior Member

thanks to the both of ya! i'll do that when i get home..
as for the #sub , i'm not i'm usingit, using the #say.. large groups get spammy this helps define who is hitting what