Zugg Software :: View topic

Newbie Joined: 06 Dec 2002 Posts: 5 Location: USA

Hi all,

I've been having a problem with triggers that's been increasingly frustrating me. At times, my triggers will simply not go off, and other times they will go off too often, like 10 times in a row for one pattern! To jump right into the details, I'm basically dealing with 5 triggers.

1 - seems to work ok most of the time but occasionally I will try to inspire myself multiple times per pattern.
Pattern - You no longer feel inspired.
Value - Inspire me (Buff spell basically)

2a - This trigger is time-based, it goes off every 3 minutes
Pattern - You forage for a javelin for awhile, but cannot find suitable material.
Value - #wait 180000
Value - forage for @forage
2b - These two triggers seem to work ok most of the time, but more commonly the value for another of my triggers seems to attach itself to it
Pattern - You forage for a while, collect some materials, and construct
Value - #wait 180000
Value - forage for @forage

3 - This trigger is basically a psionic tick trainer to raise my character's psionic skills. All too frequently it will attach itself multiple times or go off multiple times for only a single pattern
Pattern - Your energies have built to a sufficient point
Value - out
Value - rest
Value - #wait 30000
Value - walk (This is an alias I created to enact the psionic power)

4 - This last trigger basically initiates the psionic one again in the event my concentration is broken. When using the above psionic, any command will break my concentration, so sometimes the forage/inspire triggers cancel it out
Pattern - Your concentration is broken.
Value - #wait 30000
Value - walk

Is there some sort of conflict going on here? I use these primarily to train my Ranger's guild and association skills, and it's very frustrating to wake up in the morning to see either I've run out of spirit (spell points) because the psionic triggers were going off 10 times in a row for some reason, or they simply stopped functioning at all. I'm running the latest 6.38 Beta, but to be honest this problem has been going on for several versions now. Any help would be greatly appreciated!

-Pyradius

Novice Joined: 15 Jul 2001 Posts: 31 Location: USA

Part of this could be caused by the change to the #wait command.

What you could try however is adding in a #var statement. Since you didn't say what the mud responce after you type in : 'inspire me' I'll just have to wing it *grin*

You send: inspire me
Mud reply: You feel great inspiration
Now, put that 'You feel great inspiration' into new trigger..
TrigPattern: You feel great inspiration
TrigCommand: inspired = 1

So then when the mud sends : You no longer feel inspired.

TrigPattern: You no longer feel inspired
TrigCommand: #if(@inspired != 1) {inspire me}

You can even toss in a test to see if your PsiPoint one is in the middle of doing its thing.

#if(@inspired !=1 and @PsiAct = 0) {inspire me}

Of course, in your PsiTrigger you'd need to toggle that @PsiAct varible (I tend to use 0 for off and 1 for on)

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

The preferred command for repetitive/delayed actions is #ALARM.

1 - No idea why a trigger would fire more than once per pattern. It might be a bug in the new beta version, of course. You should probably ask about it on the BETA forum.

2 - Use a one-time alarm to provide your delay.
#TR {You forage for a javelin for awhile, but cannot find suitable material.} {#ALA +180 {forage for @forage}}

3 - Again, use a one-time alarm for the delay
#TR {Your energies have built to a sufficient point} {out;rest;#ALA +30 {walk}}

4 - And again
#TR {Your concentration is broken} {#ALA +30 walk}

LightBulb
Senior Member

Newbie Joined: 06 Dec 2002 Posts: 5 Location: USA

Thanks for the replies. I never was very good at the "if-then type" triggers although I wanted to learn. Having some examples helps a lot. Thanks again, I will give them a shot!

-Pyradius

Newbie Joined: 06 Dec 2002 Posts: 5 Location: USA

Okay, been playing around with alarms at the moment. I screwed up and it ended up cumulatively adding to itself. How do you set an alarm to only go off once?

Do you just make a trigger that deletes itself after going off once? I recall reading a bit on that in the help-file, but couldn't find anything specific to one-time alarms.

-Pyradius

Newbie Joined: 06 Dec 2002 Posts: 5 Location: USA

Sorry, figured out my own question, didn't realize that's what the brackets were for! Cheers!

-Pyradius

Newbie Joined: 06 Dec 2002 Posts: 5 Location: USA

Just as an update, the one time alarms are great! Inspire seems to be working okay on it's own, apparently the conflict was between the multiple wait commands I had going I guess, because I have them all playing nicely together! Thanks again!

-Pyradius