 |
Delgar
Beginner
Joined: 22 Dec 2008
Posts: 21
|
 Posted: Fri Mar 13, 2009 8:32 pm
(Fixed) [3.05] #ECHO not always interpreting <color> codes from triggers
|
I have a number of triggers using #ECHO and <color> codes that work perfectly ok in versions prior to 3.05,
but now they don't change the color and output the <color> as text.
It appears that it only occurs when the trigger fires from mud output rather than another echo.
Here is the code for a simple trigger that does the same thing as my other "broken" triggers:
| Code: |
#TRIG TEMP_TEST {appears in the room.} {#ECHO {<color orange>This is a simple test.</color>}}
|
If "appears in the room." comes from the mud, I get the following output:
<color orange>This is a simple test.</color>
If I do "#ECHO {appears in the room.}", the text "This is a simple test." shows up in
orange just like I expect.
The compiled code is:
| Code: |
0000 PUSHSTRLOC 0016
0008 JUMP 0068
0016 STR '<color orange>This is a simple test.</color>'
0068 CMD echo (1)
|
Let me know if you need additional information.
Thanks,
-- Delgar |
|
Last edited by Delgar on Sat Apr 18, 2009 9:37 pm; edited 1 time in total |
 |
|
|
Rahab
Wizard
Joined: 22 Mar 2007
Posts: 2320
|
Posted: Fri Mar 13, 2009 8:47 pm
|
This sounds odd, but could you try opening your options, and on the Preferences window, under MXP, marking the checkbox for Force Remote MXP?
I doubt that this was intended to work this way, but this new checkbox may be having unexpected side-effects. |
|
|
|
|
Delgar
Beginner
Joined: 22 Dec 2008
Posts: 21
|
Posted: Fri Mar 13, 2009 9:08 pm
|
Yes, that did the trick.
The triggers are firing and the #echo text is being colorized correctly again.
Thanks for the quick suggestion/fix. |
|
_________________
Thanks,
-- Delgar |
|
|
|
Dumas
Enchanter
Joined: 11 Feb 2003
Posts: 511
Location: USA
|
Posted: Fri Mar 13, 2009 11:09 pm
|
I'm finding that if you are playing a MUD that doesn't have its own MXP support, you must select the Force option to do your own MXP commands.
|
|
|
|
|
Delgar
Beginner
Joined: 22 Dec 2008
Posts: 21
|
Posted: Fri Mar 13, 2009 11:42 pm
|
Why would the MUD having MXP support affect the #ECHO CMUD command?
Is it that the #ECHO is pushed through the same processing as MUD output to allow triggers to
react to the #ECHO output as if it were coming from the MUD?
If that is the case, even a MUD with MXP support is going to have to have the "Force Remote MXP"
option marked to have CMUD actually process #ECHO MXP (since the #ECHO output doesn't go to
the MUD, the MUD's MXP processing won't do anything with it), or am I wrong on this? |
|
_________________
Thanks,
-- Delgar |
|
|
|
Dumas
Enchanter
Joined: 11 Feb 2003
Posts: 511
Location: USA
|
Posted: Fri Mar 13, 2009 11:53 pm
|
Ahh, yes. Even though I wasn't stating it as a specific response to yours and more of a general obsevation. I did the plain echo in a blank session and it got the colored text even without the Force option checked. Which means I do not know why it didn't work with mud text. Sorry about that.
Hmm, I tried the full trigger and used #SHOW %concat("appears"," in"," the"," room.") to test it, and it didn't work (received <color orange>This is a simple test.</color> as the response) when not forced. |
|
|
|
|
Dumas
Enchanter
Joined: 11 Feb 2003
Posts: 511
Location: USA
|
Posted: Sat Mar 14, 2009 12:03 am
|
Here was the note for the option
| Quote: |
| MXP: Added new "Force remote MXP" option to determine if MXP is enabled for the remote server even if the remote server does not negotiate MXP. This option is now DISABLED by default to prevent CMUD from parsing MXP by mistake from MUDs without MXP support. To restore the previous operation of CMUD, turn this option on. Having this option disabled makes CMUD more compliant with other MXP clients |
It appears that even though this option is defaulted to disabled, that it only needs to be disabled if there is an issue with non-MXP muds?
Now, if user defined MXP tags should still work no matter the status of this option, then it may be a bug. |
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Sat Mar 14, 2009 12:22 am
|
| Dumas wrote: |
| if user defined MXP tags should still work no matter the status of this option, then it may be a bug. |
They should, so it sounds like it. |
|
|
|
|
Rahab
Wizard
Joined: 22 Mar 2007
Posts: 2320
|
Posted: Mon Mar 16, 2009 5:15 pm
|
Yes, the description you gave made me suspect a bug of exactly the type you suggest, which is why I suggested trying that checkbox. It's a new option, so bugs are quite possible.
|
|
|
|
|
Delgar
Beginner
Joined: 22 Dec 2008
Posts: 21
|
Posted: Sat Apr 18, 2009 9:36 pm
|
Confirmed fix that 3.06 color flags on #echo in triggers works correctly without having to have the "Force remote MXP" option set.
|
|
|
|
|
|
|
|
