Register forum user name Search FAQ

Gammon Forum

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 ➜ Triggers firing on triggers

Triggers firing on triggers

It is now over 60 days since the last post. This thread is closed.     Refresh page


Posted by Colarmel   (3 posts)  Bio
Date Sun 15 Jan 2006 07:28 AM (UTC)
Message
I'm setting up a series of triggers to pick boxes in the mud I play, each box has three discriptors, the idea is to almost fully automate the process with the results of one trigger causing the others to fire, but instead I'll enter the initial command, and the next trigger in line wont fire. and I'm using the exact same triggers with the exact same version of MUSHclient as someone else on my mud, but here they are if they help.

<triggers>
<trigger
enabled="y"
group="Chests"
match="* carried A * * *, which falls to the ground."
name="ChestStorage"
sequence="100"
>
<send>put all.%4 back</send>
</trigger>
<trigger
enabled="y"
group="Chests"
match="A spray of fire leaps out to sear your *, burning a * * * like kindling!"
name="ChestTrap2"
sequence="100"
>
<send>get %2 backpack</send>
</trigger>
<trigger
enabled="y"
group="Chests"
match="A sudden explosion against your * and shattering a * * * to splinters!"
name="ChestTrapExplode"
sequence="100"
>
<send>get %2 backpack</send>
</trigger>
<trigger
enabled="y"
group="Chests"
match="With a *snap* your * breaks off inside the lock."
name="GetLockpick"
sequence="100"
>
<send>get lock sheath
wear lock</send>
</trigger>
<trigger
enabled="y"
group="Chests"
match="You pick the lock on a *."
name="LockPicking"
>
<send>open '%1'
get all '%1'
drop '%1'
sac '%1'</send>
</trigger>
<trigger
enabled="y"
group="Chests"
match="a * * * doesn't appear to be trapped."
name="NoTrap"
sequence="100"
>
<send>pick %1</send>
</trigger>
<trigger
enabled="y"
group="Chests"
match="A * * * doesn't appear to be trapped."
name="NoTrap2"
sequence="100"
>
<send>pick %1</send>
</trigger>
<trigger
enabled="y"
group="Chests"
match="You release and drop a * * *."
name="PickContinue"
sequence="100"
>
<send>get %1 backpack
unarm %1</send>
</trigger>
<trigger
enabled="y"
group="Chests"
match="You attempt to pick the lock on a * * *, but fail."
name="PickFail"
sequence="100"
>
<send>pick %1</send>
</trigger>
<trigger
enabled="y"
group="Chests"
match="You failed."
name="PickFail2"
sequence="100"
>
<send>!</send>
</trigger>
<trigger
enabled="y"
group="Chests"
match="You attempt to unarm the trap on a * * *, but manage to spring it instead!"
name="PickSpring"
sequence="100"
>
<send>pick %1</send>
</trigger>
<trigger
enabled="y"
group="Chests"
match="You fiddle with the trap on a * * * until you manage to render the mechanism useless!"
name="TrapPicking"
sequence="100"
>
<send>pick %1</send>
</trigger>
<trigger
enabled="y"
group="Chests"
match="You attempt to unarm the trap on a * * *, but can't quite figure out the mechanism."
name="UnarmFail"
sequence="100"
>
<send>unarm %1</send>
</trigger>
<trigger
enabled="y"
group="Chests"
match="You get a * * * from A black leather backpack."
name="UnarmStart"
sequence="100"
>
<send>unarm %1</send>
</trigger>
</triggers>
Top

Posted by Nick Gammon   Australia  (23,173 posts)  Bio   Forum Administrator
Date Reply #1 on Sun 15 Jan 2006 11:15 PM (UTC)
Message
Can you now post the output from the MUD that is not working for you, so we can see what is happening?

- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top

Posted by Colarmel   (3 posts)  Bio
Date Reply #2 on Tue 17 Jan 2006 12:17 AM (UTC)
Message
here's the output, the commands that follow <5009hp 2505m 2003mv> are the ones I input, the ones that are immediately after the mud generated output are from the triggers. the problem is that the trigger only fires on the results of commands I gave, not on the results of other triggers.

<5009hp 2505m 2003mv> get strong back
You get a rusted brass-bound strongbox from A black leather backpack.unarm rusted

<5009hp 2505m 2003mv> You attempt to unarm the trap on a rusted brass-bound strongbox, but can't quite figure out the mechanism.

<5009hp 2505m 2003mv> unarm strong
You attempt to unarm the trap on a rusted brass-bound strongbox, but can't quite figure out the mechanism.unarm rusted

<5009hp 2505m 2003mv> You fiddle with the trap on a rusted brass-bound strongbox until you manage to render the mechanism useless!

<5009hp 2505m 2003mv> pick strong
You pick the lock on a rusted brass-bound strongbox.open 'rusted brass-bound strongbox'
get all 'rusted brass-bound strongbox'
drop 'rusted brass-bound strongbox'
sac 'rusted brass-bound strongbox'

<5009hp 2505m 2003mv> You open a rusted brass-bound strongbox.

<5009hp 2505m 2003mv> You get a tiny shiny bluish-colored quartz from a rusted brass-bound strongbox.
You get a large shiny demantoid garnet stone from a rusted brass-bound strongbox.
You get a medium flawed milky-white pearl from a rusted brass-bound strongbox.
You get 69 copper, 0 silver pennies, 3 marks, and 0 gold from a rusted brass-bound strongbox.

<5009hp 2505m 2003mv> You release and drop a rusted brass-bound strongbox.

<5009hp 2505m 2003mv> get strong back
You get a rusted brass-bound strongbox from A black leather backpack.unarm rusted
Top

Posted by Nick Gammon   Australia  (23,173 posts)  Bio   Forum Administrator
Date Reply #3 on Tue 17 Jan 2006 04:29 AM (UTC)
Message
You are matching on:


You attempt to unarm ...


But you are getting:


<5009hp 2505m 2003mv> You attempt to unarm ...


Either change your prompt to have a newline at the end, or build the prompt into the trigger.

- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top

Posted by Colarmel   (3 posts)  Bio
Date Reply #4 on Tue 17 Jan 2006 05:00 AM (UTC)
Message
oh. *feels silly* thanks.
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,225 views.

It is now over 60 days since the last post. This thread is closed.     Refresh page

Go to topic:           Search the forum


[Go to top] top

Information and images on this site are licensed under the Creative Commons Attribution 3.0 Australia License unless stated otherwise.