|
Aell Newbie
Joined: 05 Aug 2008 Posts: 4
|
Posted: Tue Aug 05, 2008 7:01 pm
Window problems. |
I've never really used any other client before apart from MUSHclient and recently switched to CMUD for the seperate windows.
Used the following code to catch channels and send them to the window:
Code: |
#TRIGGER {(ConlegiumSicariorum)*wisps} {#CAP tells;#GAG} |
This works fine in capturing the text but the colours provided by the MUD, Discworld, get messed up:
Normally, everything on the channel is coloured the same as the first bit, but as soon as it's captured into the window it goes weird like that. Anyone have any suggestions as to why this is happening? Any help would be greatly appreciated. Thanks. |
|
|
|
Toxic Adept
Joined: 27 May 2008 Posts: 299
|
Posted: Tue Aug 05, 2008 9:19 pm |
Not sure what is the deal with your coloring but your trigger pattern is not written correctly... It may work, but only by accident... Use this instead...
#TR {^~(ConlegiumSicariorum~) %w wisps} {#CAP tells;#GAG} |
|
|
|
charneus Wizard
Joined: 19 Jun 2005 Posts: 1876 Location: California
|
Posted: Tue Aug 05, 2008 11:08 pm |
It doesn't work by accident. It's not anchored, and it matches exactly what's there. The only thing is, it's "capturing" "ConlegiumSicariorum" as %1 parameter.
) Sterling wisps: matches the *wisps part, so the trigger being matched is ConlegiumSicariorum) Sterling wisps: blah blah blah.
If it were ^(ConlegiumSicariorum)*wisps - Then it wouldn't match *shrug*
Change it to what Toxic offered.
Charneus |
|
|
|
Seb Wizard
Joined: 14 Aug 2004 Posts: 1269
|
Posted: Wed Aug 06, 2008 2:55 am |
Well, we don't know what the original colours are so we can't make a lot of judgements, but maybe you have other triggers colouring bits?
|
|
|
|
Aell Newbie
Joined: 05 Aug 2008 Posts: 4
|
Posted: Thu Aug 07, 2008 2:52 pm |
Those are the original colours provided by the mud. The only colour trigger I have is one that matches playerkillers names and colours them according to guild.
Code: |
#TR {their name} {#CW bold,color} |
If I get rid of the window and don't capture the talker string, the colours are fine. It's just when capturing. |
|
|
|
Rahab Wizard
Joined: 22 Mar 2007 Posts: 2320
|
Posted: Thu Aug 07, 2008 4:39 pm |
If those are the colors that are provided by the mud, what exactly is the problem? You say:
Code: |
as soon as it's captured into the window it goes weird like that. |
Weird like what? |
|
|
|
Aell Newbie
Joined: 05 Aug 2008 Posts: 4
|
Posted: Thu Aug 07, 2008 8:33 pm |
Well, normally the whole line of the text is colour, including what they say.
For example:
But when it's captured to a window, it does:
|
|
|
|
Toxic Adept
Joined: 27 May 2008 Posts: 299
|
Posted: Thu Aug 07, 2008 8:50 pm |
Well I can tell you whats happening... Im not sure why tho... Using your origional trigger its keeping the background color for %1 only. A work around (I would assume) is to write this as your trigger...
#TR {^(~(ConlegiumSicariorum~) %w wisps~:*)} {#CAP tells;#GAGSPACE}
Try that.
I think its a bug with #CAP only keeping the backgroup color of something thats assigned to %1-%99 |
|
|
|
Aell Newbie
Joined: 05 Aug 2008 Posts: 4
|
Posted: Thu Aug 07, 2008 10:13 pm |
Hmmm, didn't work. Thanks though. :)
|
|
|
|
Seb Wizard
Joined: 14 Aug 2004 Posts: 1269
|
Posted: Fri Aug 08, 2008 2:59 am |
Try escaping the parentheses (minimizing my other changes):
Code: |
#TRIGGER {~(ConlegiumSicariorum~)*wisps} {#CAP tells;#GAG} |
|
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Mon Aug 11, 2008 5:41 pm |
Make sure your #CW trigger has a priority number that is *lower* than your #CAP trigger to ensure that CMUD colors the line before it captures it. Also, it might help to go into the MXP Preferences page and enable the "Capture MXP" option. Otherwise #capture will only transfer ANSI colors and not MXP colors.
|
|
|
|
|
|