Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are
spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the
password reset link.
Due to spam on this forum, all posts now need moderator approval.
Entire forum
➜ MUSHclient
➜ General
➜ small problem with trigger
|
small problem with trigger
|
It is now over 60 days since the last post. This thread is closed.
Refresh page
| Posted by
| Perrin
USA (31 posts) Bio
|
| Date
| Wed 23 Feb 2005 01:00 PM (UTC) |
| Message
| I am having a small problem getting a recast trigger to work right. my MUD displays failures as:
You lost your concentration while trying to cast *.
or
You lost your concentration while trying to cast * *.
for some reason i can't get this to work. It's driving me nuts because it seems so simple. |
aardwolf player | | Top |
|
| Posted by
| Ked
Russia (524 posts) Bio
|
| Date
| Reply #1 on Wed 23 Feb 2005 03:13 PM (UTC) |
| Message
| | If the trigger isn't matching then it's a trigger problem. Try using Test Trigger on it whith the exact line, as you expect it to be (not what it actually is). If that works, then your trigger is fine, no other triggers are blocking it from matching, and the problem is that the line isn't really what it looks like. In that case, inspect the line closer, maybe there's a trailing space there that you haven't noticed, maybe something else. If Test Trigger doesn't work, then run Phantom, turn tracing on and send the line from the input window to see if there are any other triggers matching on that line and blocking the one your are trying to get to work. Also check the pattern and options - maybe the trigger isn't enabled to begin with? | | Top |
|
| Posted by
| GageEndal
(14 posts) Bio
|
| Date
| Reply #2 on Wed 23 Feb 2005 10:59 PM (UTC) |
| Message
| | You actualy only need to have the first one, you don't need two for this. The Wildcard ends on a ., not a space. | | Top |
|
| Posted by
| Perrin
USA (31 posts) Bio
|
| Date
| Reply #3 on Thu 24 Feb 2005 07:52 PM (UTC) Amended on Thu 24 Feb 2005 07:57 PM (UTC) by Perrin
|
| Message
| actually i got the first one to work but on spells with two words in the name it fails because the game reads it as a target for the spell. which is why i have the second on there what i can't figure out is how to get the first trigger to scan the line but not fire unless the the second trigger doesn't match.
|
aardwolf player | | Top |
|
| Posted by
| Ked
Russia (524 posts) Bio
|
| Date
| Reply #4 on Thu 24 Feb 2005 09:07 PM (UTC) |
| Message
| | What do you mean by "scan the line"? If you want the first trigger to match the line only if the second trigger DOESN'T match, then you can simply give the second trigger sequence 99 and leave the sequence of the first one at 100. That way the second trigger will block the first one, and the first one will match only if the second one doesn't. | | Top |
|
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.
16,196 views.
It is now over 60 days since the last post. This thread is closed.
Refresh page
![[Go to top]](/images/gototop.gif)
top