Zugg Software :: View topic

Posted: Tue Apr 24, 2007 10:12 pm

I don't know if this has been mentioned before (or even if I'VE mentioned it before) but it came up in #cmud just now - I'd really love it if there were a way to log MXP tags, specifically the <color> ones. I used to log with ANSI turned on and then use Charbal's lovely plugin to convert them to HTML to make them more readable. I've since converted almost all my ANSI colouring to MXP, and it's not logged. Very pants :(

Posted: Wed Apr 25, 2007 3:06 am

I'll add this to the bug list, but it won't be done for a while. The MXP stuff is stripped early in the parsing and isn't available by the time the logger gets to it. The logger is like the trigger system...it only sees what's on the screen as text and not the raw code. The current ANSI logging recreates the ANSI colors from the colors on the screen...it doesn't actually log the real ANSI codes from the MUD.

Wizard Joined: 14 Aug 2004 Posts: 1269

So logging with ANSI switched on should reproduce the colour codes even though they colour was determined by MXP tags?

Posted: Wed Apr 25, 2007 5:53 pm

Well, not really. MXP can produce colors that ANSI cannot. So when CMUD tries to look at the color on the screen and determine which ANSI color to use, it will likely fail. Remember than ANSI can only produce 16 foreground colors. So it's not going to be able to reproduce the color that MXP created.

Posted: Wed Apr 25, 2007 7:31 pm

can it not determine the hexadecimal color codes instead of the ansi color codes?

Posted: Wed Apr 25, 2007 7:50 pm

I guess that's how it'll be changed, since Zugg agrees that it's something to be worked on. Or it could be configurable - log ANSI colours, log websafe colours, log non-websafe colours. Or something.