Zugg Software :: View topic

Beginner Joined: 10 Sep 2002 Posts: 13

Are there any know problems with triggers not working? I would say over 95% of the time they work but every once in a while a trigger just wont work? And I can not figure out why? Anyone else have this problem?

Enchanter Joined: 11 Feb 2003 Posts: 511 Location: USA

Typically, problems like this end up being either slight problems with the pattern, or the settings of the trigger(ie prompt/newline, etc).

Apprentice Joined: 22 Jul 2004 Posts: 118 Location: USA

well if it gets messed up, (like sometimes you type in something at the right second and it screws up the triggered text. ie, i have a trigger for '^A harmonic sphere around you collapses with a wooden thunk.$' and if i type 'l' or 'status' or something just in time, then it gets mixed in with that and it wont trigger

Beginner Joined: 10 Sep 2002 Posts: 13

What can I do to combat this problem? Any ideas?

Wanderer Joined: 17 Aug 2004 Posts: 98 Location: OK, USA

It may be the order of your triggers in your settings. I have a few #GAG triggers that occassionally don't fire. Since they work about 95% of the time, I figure it's most likely due to where they're stacked. They aren't necessities, so I don't worry about the 5%. If your 5% miss/non firing triggers are important then check where they're stacked in your settings to see if there's a higher listed trigger causing a conflict.

Beginner Joined: 07 Apr 2004 Posts: 12 Location: Israel

Well, if you have other things at the end/start of your pattern, just don't anchor it (^,$).

Beginner Joined: 10 Sep 2002 Posts: 13

Well nothing else is firing on the text and it looks exactly like the text that fired before.
It's hard to troubleshoot because I cannot reproduce it all the time.

Wanderer Joined: 17 Aug 2004 Posts: 98 Location: OK, USA

How about an example.

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

Ok I THINK I know what he is talking about and it can be hard to reproduce. I also don't think its way to much to worry about because after all in about 400+ lines of text it might happen once.

I have a prompt trigger for my prompt {nocr|prompt} options that Psubs my prompt and rarley I will notice that it didn't trigger this usually happens when recieving multiple prompts really fast *IE* spamming a carriage return to get multiple prompts. I (without having a clue) think the problem lies in the data that zmud recieves/sends as an example instead of getting:

incomdata1[
its getting this
incomdata1[croutdata1 // or vise versa somesuch and confusing it as one line

Maybe its something Zugg can fix maybe something not but either way I don't see the less then 5% failing worth worrying too much about

Enchanter Joined: 10 Oct 2000 Posts: 698

I have seen this occur as well. Usually it's when many triggers are firing rapidly. Most triggers work %100 of the time, but background triggers that are always on, ie. colorization, auto-emotes will sometimes miss a line or two and lag usually seems to make them miss more often, but not always.

Although I don't know why this happens, I'd suggest ordering your triggers so that the most crucial ones like for PK battles are highest on the priority list, like Falan suggested.

The last time I noticed this happen was with this script:
EXAMPLE: