Zugg Software :: View topic

Beginner Joined: 05 Feb 2005 Posts: 11

I continue to add the #If command after a trigger command so that it will execute certain variables. Perhaps I'm using it wrong, but here is the code.

Adept Joined: 30 Dec 2003 Posts: 226

The IF commands should be IN the trigger.

#TRIGGER {hp ( (%d)/633 ) sp ( (%d)/629 ) mp ( (%d)/440 )} {
#var hp_monitor {%1}
#var sp_monitor {%2}
#var mp_monitor {%3}
#If (hp_monitor < (sp_monitor - 25)) {cast 'heal light'}
#If (mp_monitor < 60) {cast 'regeneration'}
}

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

Also make sure you are qouting the special chars with ~
#TRIGGER {hp ~( (%d)/633 ~) sp ~( (%d)/629 ~) mp ~( (%d)/440 ~)}

Beginner Joined: 05 Feb 2005 Posts: 11

The #if statements stay in the trigger, but nothing happens it doesn't cast heal or regeneration. Any thoughts or ideas?

Enchanter Joined: 05 Mar 2003 Posts: 593 Location: Canada

Is the trigger firing at all?
Add an echo statement to the trigger to make sure the trigger is firing.
Also its very important to quote the special characters as nexela said.
Perhaps you could copy an example of your prompt, and post it along with a current example of the trigger?

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

Say oops missing a few things (in red) :p

#TRIGGER {hp ~( (%d)/633 ~) sp ~( (%d)/629 ~) mp ~( (%d)/440 ~)} {
#var hp_monitor {%1}
#var sp_monitor {%2}
#var mp_monitor {%3}
#If (@hp_monitor < (@sp_monitor - 25)) {cast 'heal light'}
#If (@mp_monitor < 60) {cast 'regeneration'}
}

Beginner Joined: 05 Feb 2005 Posts: 11

I've added an echo command, and it just doesn't trigger. I've also tried to add the (%d) in front of a different trigger and it just doesn't want to fire. I'm not sure why though.

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

Then it is not matching correctly

Paste your mud prompt between some[ CODE ] tags.

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

I noticed you had multiple spaces in the trigger pattern in your first post. Whenever you have multiple spaces in a line of text you want to match, you need to use the %s wildcard. Without it, the multiple spaces in the pattern are compressed down to one single space and the pattern will then not match the line.

Beginner Joined: 05 Feb 2005 Posts: 11

If I use the %s wildcard, I'll have to go %1, %3, %5, because %2 and %4 will be assigned to the wild card variable %s right?

Enchanter Joined: 05 Mar 2003 Posts: 593 Location: Canada

only things enclosed in a capturing group () are assigned to %n variables
so adding if you add a %s but dont enclose it in parenthesis then you can ignore it as far as the $1,%2,etc are concerned

Beginner Joined: 05 Feb 2005 Posts: 11

Alright, I attempted to use the %s wildcard and it still doesn't want to fire. So figuring it wasn't the spaces (I knew I had the correct amount in the first place) I tried something different. I took a trigger where I normally had a * instead of a direct variable such as (%w). So what I did was substitute the varibale (%w) for a trigger with a word in front of it, sacrifice corpse. I originally used the following:

Enchanter Joined: 05 Mar 2003 Posts: 593 Location: Canada

hey Litteron why not post the current trigger your trying to make work
along with the line you're trying to capture,
just cut input from the mud and paste it here
maybe we can catch something you maybe missing Smile

Beginner Joined: 05 Feb 2005 Posts: 11

Here is the trigger. The Mud displays the command after each attack:

hp ( 633/633 ) sp ( 629/629 ) mp ( 440/440 )

Here is the Code I use:

Enchanter Joined: 05 Mar 2003 Posts: 593 Location: Canada

Beginner Joined: 05 Feb 2005 Posts: 11

I tried that code Darkhael and it's still not firing at all. I did an echo to see if it would fire, it didn't work. I did exactly what you put, no go.

Enchanter Joined: 05 Mar 2003 Posts: 593 Location: Canada

bah I've no idea, why not, perhaps someone else might spot a mistake I made.
anyways this next code ignores whitespace all together
also instead of requiring specific numbers for the max hp,sp,mp
it accepts any number.

#REGEX {hp\s*$\s*(\d+)/\d+\s*$\s*sp\s*$\s*(\d+)/\d+\s*$\s*mp\s*$\s*(\d+)/\d+\s*$} {
#var hp_monitor {%1}
#var sp_monitor {%2}
#var mp_monitor {%3}
#If (@hp_monitor < (@sp_monitor - 25)) {cast 'heal light'}
#If (@mp_monitor < 60) {cast 'regeneration'}
}

Beginner Joined: 05 Feb 2005 Posts: 11

WOO... Finally it worked. But I'd still like to know the problem with what happened, because of other triggers I have, but also so I can code them in the future. Perhaps I'll just attempt to figure out how to use #Regex but I'm not too familiar with those type of Unix commands. Either way we'll see. Maybe someone else sees the problem in my previous script though?

Enchanter Joined: 10 Oct 2000 Posts: 698