Zugg Software :: View topic

Beginner Joined: 14 Sep 2004 Posts: 17

I'm using quite a few advanced trigger states. I noticed that when you filter for a certain string in your settings, the advanced trigger states aren't searched. This can get quite confusing when you're using a lot of advanced trigger states. You have to remember which triggers have them, and you have to find it manually. Is there any way to fix this, or make it easier?

Also, I'm using a script that runs 24/7. I use the #alarm command a lot. When I attack something, it gives me a round time:

[Round: 10 seconds]

I use #alarm +10 {stuff here} to perform commands at the perfect time. The only problem with this is, after the script runs for a long time (usually longer than a day), I can hit ctrl-g, do a search for +, and there are THOUSANDS of alarms stuck in limbo. This is bogging my system down enormously. What am I doing wrong? How come there are so many of them?

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

As for your second question

NAME your alarms and Temp triggers this will ensure that they get overritten

Example

#TRIGGER {Round: (%d) seconds} {#ALARM "Rtime" {+%1} {#SAY Rtime up!}}

Beginner Joined: 14 Sep 2004 Posts: 17

Awesome, that should help a lot.

I wonder if there will ever be a solution for my first question.

Beginner Joined: 08 Apr 2004 Posts: 24 Location: USA

My solution (Where the hell is the search function?) is that I put everything into specific folders, and sub folders. From that I can find them, but maybe my brain just works better that way.

Apprentice Joined: 29 Jun 2001 Posts: 198 Location: USA

Posted: Thu Nov 11, 2004 9:20 am

Just to add what Ratalon said. I find it much easier to maintain my scripts by using something similar to a filesystem. I rarely use the search function. When i do use the search function i use it to indicate which folder the #trigger, #alias is in. I then highlight that particular class folder and change to the tab called class scripts which then displays everything in that folder in a easily read
scripted view. You can then see which triggers have states etc.