Zugg Software :: View topic

Posted: Sat Sep 29, 2007 5:20 pm

I have the following trigger in a module so all my windows can use it:

#CW mage dodgerblue

Then this in my child window to provide a timestamp:

#TR {^} {#SUB {%time(t)}}

And this to capture to said child window:

#TR {<mage>} {#CAP Tells}

You would expect a line like:

Name <Mage> message

to be captured to the window as:

timestamp Name <Mage> message

but instead its coming out (at least part of the time) as:

Name <timestamp> message

For some reason, the timestamp is being placed where the colored text should go instead of at the beginning of the line.

P.S. I have disabled MXP in both the main and child windows.

Wizard Joined: 14 Aug 2004 Posts: 1269

Looks like the same problem as: [2.04] Trigger intermittently matches the line after the line that it should do

I'm going to try disabling my trigger that adds a timestamp to the beginning of my prompt and see if that helps...

Wizard Joined: 14 Aug 2004 Posts: 1269

Posted: Sat Sep 29, 2007 8:30 pm

For me its the carat trigger, i guess it doesn't like subbing out a null length.

Wizard Joined: 14 Aug 2004 Posts: 1269

1. Re-enabled prompt trigger without #SUBs and it seems to be fine too.
2. Re-added #SUB, but changed it to use "NoTime" instead %time( hh:mm:ss) and it still seems to be fine, so it looks like it may be an interaction of the %time function.
3. Changing "NoTime" to be "01:23:45" to be sure.

Wizard Joined: 14 Aug 2004 Posts: 1269

Wizard Joined: 14 Aug 2004 Posts: 1269

Hmm, the weirdness has come back for me. I guess it's not %time. Maybe it's just a timing issue that is more likely to occur when several things are happening at once, like using a #CAPTURE followed by a #SUB.

Enchanter Joined: 09 Sep 2007 Posts: 605

Shalimar, had you this problem in 2.03? Heh, I almost ready to ask everybody not to edit their settings if they don't work in 2.04 and did work in 2.03. Sad...

Enchanter Joined: 09 Sep 2007 Posts: 605

I have a standard set of triggers for capturing talks, gossips, newbie, shouts, grouptells, etc... These are the same triggers I have in zMUD 3.xx almost 10 years ago, now they are here, in CMUD. They work excellent, until this 2.04. Now I also have strange output from them (or I must say have almost nothing from them?) Here is the sample:

Wizard Joined: 14 Aug 2004 Posts: 1269

Yeah, it looks like there is a problem when using #SUB and #CAPTURE within a very short time frame of each other. I didn't have the problem in v2.03.

Wizard Joined: 14 Aug 2004 Posts: 1269

Wizard Joined: 14 Aug 2004 Posts: 1269

Hmm, and it hasn't done it at all since.

Wanderer Joined: 14 Jul 2004 Posts: 83

I have a similar trigger that doesn't use substitution. It's there to #gag a Hints channel until one of three specific hints comes across. This worked fine until I upgraded to 2.04 about 40 minutes ago. Now it's gagging the prompt line that would normally come after the hint line.

It did not start doing this immediately upon connection. In fact, it took about 30 minutes before it started showing up like this.

I don't have 1 trigger to handle all the different hints. Instead, I have 1 trigger per hint line. There is no #sub command to it, just the #gag.

Wizard Joined: 14 Aug 2004 Posts: 1269

Does it also use #CAPTURE? (Or #WINDOW?)

Wanderer Joined: 14 Jul 2004 Posts: 83

This particular set does not. It exists solely to #GAG the Hints that I don't want to see.

However, this bug is also affecting the chat triggers that #CAPTURE as well as #GAG. My prompt line gets #CAPTUREd to the chat window instead of the channel.

Wizard Joined: 14 Aug 2004 Posts: 1269

Hmm, I don't use #GAG in mine, so there doesn't appear to be a single common denominator...

Posted: Mon Oct 01, 2007 9:24 am

Mine isnt gagged either, but if i turn off the carat trigger, it runs fine.

Wizard Joined: 14 Aug 2004 Posts: 1269

Hmm, well my capture trigger doesn't use a carat, but my prompt trigger does. Both also use #SUB.

Posted: Mon Oct 01, 2007 9:36 am

My capture doesnt use the carat either... that was a separate trigger inside the window.
It captures just fine with or without the carat trigger enabled.
But when it is enabled, the timestamp, which is supposed to be at the biggining of the line, gets moved to where the highlighted text should be.