 |
Azza1
Newbie
Joined: 03 Jun 2003
Posts: 2
Location: Australia
|
 Posted: Tue Jun 03, 2003 3:46 pm
Trigger outputs { }
|
Hi- I've just upgraded to 6.62 and my triggers are working okay but when it outputs the result of the trigger back the mud it does it with { } around it. Which the mud doesn't like ie - bad command.
********************************************
Trigger is as follows -
A small (%w) stone has been wedged there.
#if (%1=jade) {
imitate owl
climb rope
}{}
#if (%1=azure) {
imitate wolf
climb rope
}{}
#if (%1=amber) {
imitate hawk
climb rope
}{}
#if (%1=moon) {
imitate fox
climb rope
}{}
#if (%1=fire) {
imitate cougar
climb rope
}{}
**************************************************
If anyone of the above statements is true then it outputs text back to the mud but the text has the curly braces around it and therefore it fails.
Eg the output to the mud looks like this
{imitate cougar;climb rope}{}
The question is how do I get rid of the curly braces in the output?
Thanks
Az |
|
|
|
|
Lalaynya
Wanderer
Joined: 23 Aug 2002
Posts: 96
|
Posted: Tue Jun 03, 2003 4:23 pm
|
Putspacesbetweenthecurlybraces,otherwisetheclientdoesn'tunderstandwhatyoumean.
like this:
} { } not: }{} |
|
|
|
|
DeathofOne
Beginner
Joined: 03 Jun 2003
Posts: 25
|
Posted: Tue Jun 03, 2003 4:23 pm
|
Why do you have basic so you understand
#if (x = y) {I hate all} <{}>
The stuff inside <> is not inportant.
if you are going to do a if comand you do not need the false. Do this if this but do nothing if something else. You do not need the no nothing. |
|
|
|
|
Azza1
Newbie
Joined: 03 Jun 2003
Posts: 2
Location: Australia
|
Posted: Tue Jun 03, 2003 4:32 pm
|
Yep that was to easy. It was the space between the curly braces that fixed it.
And to answer the question of why have true and the empty false curly braces...well I just think it rounds out the statement :) ...in some of my triggers in I have false statements doing things.
Thanks for the help
Az |
|
|
|
|
|
|
|
