Zugg Software :: View topic - [2.33] #UNTRIGGER bugs - one in events, other in aliases w/ classes

Apprentice Joined: 24 Jul 2008 Posts: 109

I can't figure out what I'm doing wrong. The second trigger -- the longest one -- won't untrigger properly, but the first and third untrigger fine. Here are the triggers:

#TRIGGER {{Vocals:%s%d %d.%d~% mind lock|Vocals:%s%d %d.%d~% dazed}} {#VAR voclock 1;#WAIT 200000;#EXECUTE {queue exp skill vocals}}

#TRIGGER {{Vocals:%s%d %d.%d~% clear|Vocals:%s%d %d.%d~% learning|Vocals:%s%d %d.%d~% thoughtful|Vocals:%s%d %d.%d~% pondering|Vocals:%s%d %d.%d~% concentrating|Vocals:%s%d %d.%d~% muddled|Vocals:%s%d %d.%d~% very|Vocals:%s%d %d.%d~% perplex|Vocals:%s%d %d.%d~% bewilder}} {#VAR voclock 0;#EXECUTE {queue hum scales}}

#TRIGGER {^You finish humming} {#EXECUTE {queue exp skill vocals}}

And the untriggers:

#UNTRIGGER {{Vocals:%s%d %d.%d~% mind lock|Vocals:%s%d %d.%d~% dazed}}

#UNTRIGGER {{Vocals:%s%d %d.%d~% clear|Vocals:%s%d %d.%d~% learning|Vocals:%s%d %d.%d~% thoughtful|Vocals:%s%d %d.%d~% pondering|Vocals:%s%d %d.%d~% concentrating|Vocals:%s%d %d.%d~% muddled|Vocals:%s%d %d.%d~% very|Vocals:%s%d %d.%d~% perplex|Vocals:%s%d %d.%d~% bewilder}}

#UNTRIGGER {^You finish humming}

I made the untriggers by copying and pasting the triggers. They show up in the script just how they do there, one right after the other. All three trigger fine, but when it gets to the point of untriggering the middle untrigger does not untrigger, only the one before and after it untrigger. That's the end of the script and there is nothing that reinstates the second trigger or anything, and I don't even get the echo back that it's ever been untriggered when the other two are untriggered. Furthermore, if I try giving the second trigger a name and untriggering it by name instead of the pattern, it still does not work.

And the kicker is that if I copy and paste the second untrigger into the command line, it untriggers the trigger fine. Why can I do it manually and it does not work in the script? This is driving me batty, thanks for any help. :(

Apprentice Joined: 24 Jul 2008 Posts: 109

Okay, here's an interesting thing...

I had this as an event. If I ran the end of the event a second time, it would untrigger that trigger properly. (The other two were already untriggered.) On the whole it was behaving oddly.

So I copy and pasted the entire thing to an alias. I didn't change a single character. Instead of raising the event, I executed the alias. It works perfectly.

Do I not understand something important about events? :-/

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

You should name triggers if you want to refer to them later.

#TRIGGER blah {{Vocals:%s%d %d.%d~% mind lock|Vocals:%s%d %d.%d~% dazed}} {#VAR voclock 1;#WAIT 200000;#EXECUTE {queue exp skill vocals}}
#UNTRIGGER blah

I think that's the syntax anyway, I don't have CMUD installed anywhere atm

Apprentice Joined: 24 Jul 2008 Posts: 109

You can untrigger using the pattern or a name. But like I said, neither works, and for some reason it works perfectly as an alias but not an event.

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

Ah sorry, I must've started writing my reply before I saw your 2nd post.
You may have found a bug by the look of it if #EVENT doesn't let you untrigger something.

Apprentice Joined: 24 Jul 2008 Posts: 109

I think it must be an event thing, because, come to think of it, I had a similar problem untriggering something a few days ago. I found a different way to write that event so I didn't post then.

Here's the full text of the stuff that works fine as an alias, but not as an event. It's a shame, too, because I'd really much rather this be an event... I have to run the event with a variable twice to get it to untrigger the trigger, i.e. to execute the "else" so it unvars and untriggers everything. (The first time, it unvars untriggers everything but the second trigger. The second time, it untriggers only the remaining second trigger.)

One interesting thing to note is that, while I was tinkering with it, I discovered I could change which trigger would not untrigger properly by making slight changes to the triggers above, and anything else that moved the line numbers around. So, for example, if I changed one of the triggers to have a #VAR assignment in it, and it was long enough to go wrap over a line, sometimes the second trigger would untrigger properly and then the first or last one wouldn't. I ensured that it was wrapping and there weren't any carriage returns or anything. Seems really weird.

#IF (%1=="") {#TRIGGER {{Vocals:%s%d %d.%d~% mind lock|Vocals:%s%d %d.%d~% dazed}} {#WAIT 200000;#EXECUTE {queue exp skill vocals}}

#TRIGGER {{Vocals:%s%d %d.%d~% clear|Vocals:%s%d %d.%d~% learning|Vocals:%s%d %d.%d~% thoughtful|Vocals:%s%d %d.%d~% pondering|Vocals:%s%d %d.%d~% concentrating|Vocals:%s%d %d.%d~% muddled|Vocals:%s%d %d.%d~% very|Vocals:%s%d %d.%d~% perplex|Vocals:%s%d %d.%d~% bewilder}} {#EXECUTE {queue hum scales}}

#TRIGGER {^You finish humming} {#EXECUTE {queue exp skill vocals}}

#EXECUTE {queue exp skill vocals}
} {#EXECUTE {queue stop hum}

#UNTRIGGER {{Vocals:%s%d %d.%d~% mind lock|Vocals:%s%d %d.%d~% dazed}}

#UNTRIGGER {{Vocals:%s%d %d.%d~% clear|Vocals:%s%d %d.%d~% learning|Vocals:%s%d %d.%d~% thoughtful|Vocals:%s%d %d.%d~% pondering|Vocals:%s%d %d.%d~% concentrating|Vocals:%s%d %d.%d~% muddled|Vocals:%s%d %d.%d~% very|Vocals:%s%d %d.%d~% perplex|Vocals:%s%d %d.%d~% bewilder}}

#UNTRIGGER {^You finish humming}
}

As an event, I would use "#RAISE vocals", and "#RAISE vocals end" to clear everything out. Buggy. As an alias, I use "vocals", or "vocals end", or "#EXECUTE {vocals}", or "#EXECUTE {vocals end}" and it works just fine. Except, of course, that it's not an event like I want it to be. :(

Apprentice Joined: 24 Jul 2008 Posts: 109

Okay, there is a bug with this as an alias as well. The next-to-last trigger will not untrigger if I put the triggers in a class and then untrigger it specifying the class. All the other triggers will untrigger, but not that one. It just sits in the class.

What doesn't work:
- Unlike with the event, running the section of the script that untriggers everything a second time will not remove that remaining untrigger.

- Unlike with the event, copying and pasting the #UNTRIGGER {pattern} class and executing it manually from the command line does not work properly.

What works:
- If I remove the class specification from that one trigger, it will untrigger it. So #UNTRIGGER {pattern} class does not work, but #UNTRIGGER {pattern} works.

- Unlike with the event bug, naming the trigger does make a difference here. I can #UNTRIGGER triggername class and it will work. This is the only way to untrigger the trigger specifying its class.

The alias is named vocals.

This is the code without any classes involved, and everything works:

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

At the moment the title doesn't read like a bug report, to try and get Zugg's attention I'd suggest renaming the thread to

[2.33] Cannot #UNTRIGGER from within an #EVENT

or similar
(I'm assuming you're using the latest version btw)

Apprentice Joined: 24 Jul 2008 Posts: 109

Thanks, I changed the title. :-) I think I've got another example of the alias in classes things to post in a moment, it seems to happen to me frequently.

Apprentice Joined: 24 Jul 2008 Posts: 109

Yeah, here we go again, haha. Some #UNTRIGGER {pattern} class commands work properly while others randomly don't. Manually executing them from the command line does not work. Giving them names and then using #UNTRIGGER name class works.

In this script, the triggers that would not untrigger properly are the ones given names: lame1, lame2, and lame3. Below the #UNTRIGGER name class for these buggy triggers I have commented out the #UNTRIGGER {pattern} class that, inexplicably, did not work.

The triggers are all near the top and the untriggers are all near the bottom. I included the rest in case I screwed something strange up and that's what's causing the bug.