Zugg Software :: View topic

Adept Joined: 20 Jul 2004 Posts: 268

Trying to get a stat reporter running a little automatically.
I want to type stats have it send attr and then on the line (Use 'SCORE' and 'WHOIS' to see more details on your character) have it send the results to whatever i typed after stats (stats clan sends the report to the clan channel etc.)
The code works fine, but for SOME reason it's copying the trigger that I want it to go off of in the main class folder, so when i type attr it is sending the command regardless.
Not sure why at all.

The output of attr from the mud varies from how people might have it set up. it will either be:

Adept Joined: 20 Jul 2004 Posts: 268

K did some work on this and made it work, but as far as i am concerned it's ugly as hell..If someone could show me how to clean it up a little it would be great.

#CLASS {Stat_Announce}
#ALIAS stats1 {
#va stat1ann {%1 %2}
#T+ pissingmeoff
attr
}
#TRIGGER {^Str :~[%1~/%2~] * :~[%3~/%4~] *:~[%5~/%6~] *r :~[%7~]} {
#var spelled_str {%1}
#var base_str {%2}
#var spelled_int {%3}
#var base_int {%4}
#var spelled_wis {%5}
#var base_wis {%6}
#var att_hr {%7}
}
#TRIGGER {^Dex :~[%1~/%2~] * :~[%3~/%4~] *:~[%5~/%6~] *r :~[%7~]} {
#var spelled_dex {%1}
#var base_dex {%2}
#var spelled_con {%3}
#var base_con {%4}
#var spelled_luck {%5}
#var base_luck {%6}
#var att_dr {%7}
}
#TRIGGER "pissingmeoff2" {---------------------------------------------------------------------------} {
@stat1ann Bunches of cute info that seem to be worth knowing to others
#T- pissingmeoff
#T- pissingmeoff2
} "" {disable}
#TRIGGER "pissingmeoff" {Your main attributes are:} {#T+ pissingmeoff2} "" {disable}
#CLASS 0

Used Pretty Print
Syntax Colourizer

Adept Joined: 30 Dec 2003 Posts: 226

If you wanted to use the original script you had, you could have changed the "#TRIGGER {(Use score..." to #TEMP {(Use score...

Temp triggers only fire once, so you wouldn't have it reporting every time you hit stat. As for a cleaning up the second one, I would suggest looking at using conditions.

Adept Joined: 30 Dec 2003 Posts: 226

Something like:

#CLASS {Stat Announce}
#ALIAS stats1 {
#VAR stat1ann {%1 %2}
#T+ statann
}
#VAR stat1ann {}
#VAR spelled_str {}
#VAR base_str {}
#VAR spelled_int {}
#VAR base_int {}
#VAR spelled_wis {}
#VAR base_wis {}
#VAR att_hr {}
#VAR spelled_dex {}
#VAR base_dex {}
#VAR spelled_con {}
#VAR base_con {}
#VAR spelled_luck {}
#VAR base_luck {}
#VAR att_dr {}
#TRIGGER "statann" {^Your main attributes are:} {}
#COND {^Str :~[(%d)~/(%d)~] * :~[(%d)~/(%d)~] *:~[(%d)~/(%d)~] *r :~[(%d)~]} {
#VAR spelled_str {%1}
#VAR base_str {%2}
#VAR spelled_int {%3}
#VAR base_int {%4}
#VAR spelled_wis {%5}
#VAR base_wis {%6}
#VAR att_hr {%7}
}
#COND {^Dex :~[(%d)~/(%d)~] * :~[(%d)~/(%d)~] *:~[(%d)~/(%d)~] *r :~[(%d)~]} {
#VAR spelled_dex {%1}
#VAR base_dex {%2}
#VAR spelled_con {%3}
#VAR base_con {%4}
#VAR spelled_luck {%5}
#VAR base_luck {%6}
#VAR att_dr {%7}
}
#COND {^Trains:} {
@stat1ann Bunches of cute info that seem to be worth knowing to others
#VAR stat1ann {}
#T- statann
}
#CLASS 0

Adept Joined: 20 Jul 2004 Posts: 268

Don't #COND's need to have a within paramater?
thought they did. *grumble*

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

no, they don't HAVE to. #CONDITION doesn't really need any parameters unless you use a specific type. As for WITHIN, that allows zmud to determine that the trigger in fact did not match and so it doesn't need to keep looking for a match.

Adept Joined: 20 Jul 2004 Posts: 268