Trigger Colors

Posted by MGH on Wed 11 Dec 2002 02:02 AM — 3 posts, 12,994 views.

#0
Until I installed 3.32, I could easily alter the output>triggers to show whatever color I chose on a <Channel> on pennmush. I'm talking @channels here.

Unfortunately, since I installed this version, I can't do that in this specific instance: <channel> * doesn't trigger when the output is anything but a pose on the channel. That is <Hardcode> MGH, says, <blah> doesn't activate the color trigger, but <Hardcode> MGH has had a bad day., does. I've been fighting with this for hours and tried various regexp's as well. The developers of pennmush tell me they detect nothing wrong with the info sent to the client.

Note this: on a MUSH using the exact same version of pennmush, but with softcoded channels, MUSHclient 3.32 operates normally: i.e, all triggers for color changes work as they are supposed to.

So my question to whoever it may concern is: when will you fix this?

MGH
USA #1
Hardcoded channels are rather notorious for resisting coloration changes in my experience. This may very well not be an issue with MC but with the hardcoded channel color selections on the mud. Depending upon where the color defs are placed in the hardcode your MC alias may very well be sending the colors you want only to have them stripped by the channel hardcode. Based on the fact that you say the exact same trigger works on a softcoded channel would seem to support the cause being the hardcode rather than anything in MC.
Australia Forum Administrator #2
Can you copy and paste your trigger, and the actual MUD output? I don't see how MUSHclient can tell the difference between softcoded and hardcoded channels, so there must be some subtlety to the text you are matching on that is causing this.