Zugg Software :: View topic - [1.34] Bug, #SUBS and trigger states not firing after #SUBS

Posted: Wed Jul 04, 2007 5:03 am

For purpose of testing and tracking this bug, I used two emotion verbs, cough and grin.

#TR {You cough softly.} {#SAY Fired}
#COND {The corners of your mouth turn up as you grin mischievously.} {#SAY Fired}

This works. Both states always fire.

#TR {You cough softly.} {#SUBS {I'm only pretending to cough.}}
#COND {The corners of your mouth turn up as you grin mischievously.} {#SAY Fired}

In this instance, it substitutes correctly with the first, but the next state will not fire. When I manually change the pattern of the second, at this point, to {The corners of your mouth turn up as you grin mischievously.$}, it will then fire when I 'grin'. If I then begin again, by 'cough'ing and then 'grin'ing, it again gets stuck on the second trigger state, until I then REMOVE the $ from the pattern.

On further testing, changing the pattern to anything (shortening it for example) or changing it to something, saving, then changing it back to its original, will make it work when I again grin.

P.S. Oh.. is there a way, within the package editor, to force a multistate trigger back to state 0? Or any state, for that matter? It took me ages to figure out to even create more states, and even then it was by chance as I went to create a new trigger altogether, and spotted it in the list. But before I figured out how to make that trig above fire by changing the pattern, I had to delete the trig and remake it, every time. I didnt think to test if #state worked.

Posted: Wed Jul 04, 2007 11:36 am

I think you used to be able to double-click on a state to select it as the current one, but you can't do that in CMUD any more. #State should work, though.

I can't reproduce your your problem from what you've given though, I'm afraid. Do you have any other settings that could be affecting this? Does this work if you use it in a new, untitled session?

Posted: Thu Jul 05, 2007 4:00 am

1. Open blank settings file in offline mode
2. Enter the following into the command line:
#TR {Pattern1} {#SUBS {Pattern one substituted.}}
#COND {Pattern2} {#SAY State 1 fired}

3. Enter "#sh Pattern1" to the command line.
4. Enter "#sh Pattern2" to the command line.
5. Observe the failure of state number 1 to fire.

6. Open up the package editor. Navigate to state one of the trigger. Add $ to end of pattern. Save. remove $ from end of pattern. Save.
7. Enter "#sh Pattern2" to the command line and observe state number 1 firing.

The output screen should read as follows:

Posted: Thu Jul 05, 2007 12:56 pm

Okay, that one's not working. Confirmed.

Posted: Thu Jul 05, 2007 5:08 pm

Confirmed and added to bug list. I have no idea what is causing this one.

Magician Joined: 25 Oct 2000 Posts: 461 Location: USA

Thanks for reporting this Caled. I ran into it last week, but didn't make the connection between #sub and the state not firing so figured I was doing something incorrect.