Zugg Software :: View topic

Apprentice Joined: 06 Apr 2004 Posts: 173

im trying to set up an alias called smoke_herb that basically sets off a multistate trigger...but i really dont understan the set and state commands...and it doesnt look like many people use a lot of them in their scripts.

if someone could help me write this i would really be greatfull.

heres the logic: NOTE: this will only be meta language as im not sure of the exact syntax...
#CLASS pipe_smoking
#VARIABLE pipe {pipe12345} {pipe12345}
#VARIABLE pipe_empty {1} {1}
#VARIABLE pipe_lit {0} {0}
#VARiABLE attempts {0} {0}
#VARIABLE has_herb_in_hand {0} {0}
#ALIAS smoke_herb {call smoke_herb_trigger}

#TRIGGER smoke_herb_trigger
state 0: {the pattern in this box is unimpotant} {attempts=0;#IF (@pipe_empty) {goto state 2} {goto state 5}}
state 1: {^You get 1 herb from your poecketbelt.$} {has_herb_in_hand=1;goto state 2}
--------if state 1 is requested but fails to match in 10 lines of text from the MUD, kick out of the trigger
state 2: {} {#IF (@has_herb_in_hand) {#SEND put herb in @pipe;goto state 3} {#SEND outb herb;goto state 1}}
state 3: {^You put an herb in your pipe.$} {pipe_empty=0;goto state 5}
--------if state 3 is requested but fails to match in 10 lines of text from the MUD, kick out of the trigger
state 4: {} {^Your pipe is lit and smoking nicely.$} {pipelit=1;goto state 5}
--------if state 4 is requested but fails to match in 10 lines of text from the MUD, kick out of the trigger
state 5: {} {#IF (@pipelit) {#SEND smoke @pipe;goto state 6} {#SEND light @pipe;goto state 4}}
state 6: {^You take a long drag off your pipe.$} {#ALARM {+115} {#ECHO WARNING: PIPE IS ABOUT TO GO OUT!!!}}
--------if state 6 is requested but fails to match in 10 lines of text from the MUD, kick out of the trigger
#CLASS 0

no matter what trigger types i put on these...and also what state and set values...i get wierd responses...any help would be very appreciated!!!

SubAdmin Joined: 18 Nov 2001 Posts: 5182

The first thing to remember about multi-state triggers is ONLY ONE state can be active at a time.

The way you described it in your meta example leads me to believe that you want more then 1 state to be active. This requires multiple triggers instead of multiple states. I think once you split up the possible repsonses to actions into an appropiate number of triggers you will find that states, for those triggers, tend to fall into place more readily.

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

#SET alters the status (fired/not fired) of the specified state. If the state is set to true (fired), then the Value of that state is executed. Also, if this is the current state and it is set to true, then the trigger advances, otherwise the current state remains unchanged. When the trigger advances, if the next state has already been set to true then it will be skipped.

#STATE sets the status of the specified state to not fired and makes it the current state.

This would probably be better as a set of individual triggers, but it's an interesting exercise.

Apprentice Joined: 06 Apr 2004 Posts: 173

Wow thanks you guys, I tried the script that LightBulb wrote...it fires and gets stuck at about state 3. I appreciate the explanation of SET and STATE go gave, they were kinda fuzzy in my mind as to whether or not you needed to use both or just one of them. Thanks Vigilante, i think i will take you up on that...and split it up into different triggers and just #T+ and #T- the devil out of them, thanks again to the both of you