Question Color

In 3.63 I cannot seem to get color to work, I have it turned on and I've tried using @@<letter>. Not sure what I'm doing wrong.

@@ was replaced with /t then the letter

like /tR = bright red

so /tRtest/tn would be bright red and the /tn would stop the color bleed.

I think im going to stay with @'s .

rudeboyrave wrote: I think im going to stay with @'s .

I find the new color system to be quite easy to use.

Liko wrote: @@ was replaced with /t then the letter

like /tR = bright red

so /tRtest/tn would be bright red and the /tn would stop the color bleed.

\t

and...

\t(HELP CLASS\t) <--- would create a basic MXP link
\t[F500]BRIGHT RED\tn
\t[F411]PINK\tn
\tPPINK\tn
\t[B005]BLUE BACKGROUND\tn
\t[U9814/Rook] <-- Create a rook icon, or display the word Rook if the player's client doesn't have that functionality
\t<SOUND FName="ouch.wav" V=50 L=2 P=80 T="combat" U=" www.yourMUD.com/sounds/ "> <-- Would play ouch.wav on an MXP/MSP capable client.
\t<send "command1|command2|command3" hint="click to see menu|Item 1|Item 2|Item 2">this is a menu link\t</SEND> <--- Will send an expandable pop-up menu, complete with mouse-over tool tip on an MXP capable client.

The editor's(MEDIT, OEDIT, etc...) still accept the '@' symbol and will parse it into a tab for proper interpretation through the protocol output function, while the improved editor requires an '/t' call, to manually toggle over any entered '@' symbol, or vise-versa.

It seems during my changes a month ago or so of setting things back to @ instead of \t , I changed something I don't remember. After seeing your last post about sound being sent with this enabled, I wanted to test it, so I went back and commented out my parse_at(dest); , But I still don't have the ability to use \t[f500] for example. My memory is failing me because I don't recall changing anything else.