 |
Dood904
Newbie
Joined: 26 Apr 2005
Posts: 2
|
 Posted: Fri Jun 23, 2006 1:40 pm
#COLOR and #CW
|
For some reason, I cannot get my #COLOR and #CW commands to work. In Zmud, you could use the $XXYYZZ format to customize your colorations. However, CMUD does not seem to be processing these custom colors.
One example off the top of my head would be just a name:
#TRIGGER {Adam} {#CW $30G890} |
|
|
|
|
Larkin
Wizard
Joined: 25 Mar 2003
Posts: 1113
Location: USA
|
Posted: Fri Jun 23, 2006 1:42 pm
|
In CMUD, the $ prefix denotes a local variable reference. As a temporary fix (i.e., until an official comment regarding whether this is a bug or a feature comes down), try converting the hex value to decimal and lose the $.
|
|
|
|
|
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
Posted: Sun Jun 25, 2006 1:52 pm
|
zMud supported using both # and $ for hexadecimal indicators with those commands. Try changing them to # and see if that works.
|
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
 |
|
|
MattLofton
GURU
Joined: 23 Dec 2000
Posts: 4834
Location: USA
|
Posted: Mon Jun 26, 2006 1:13 am
|
Have you tried quoting it?
|
|
_________________
EDIT: I didn't like my old signature |
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Jul 05, 2006 6:38 pm
|
Neither $ nor # will work. As mentioned, $ is used for local variables, and # is for command names.
I'm probably going to end up supporting the more common 0xFFFFFF syntax for hex values. Or, as Matt mentioned, you can try putting double-quotes around it to tell the parser that it's a string value and that should work too.
I'll need to add this to the list of things to convert when going from zMUD to CMUD. |
|
|
|
|
Rainchild
Wizard
Joined: 10 Oct 2000
Posts: 1551
Location: Australia
|
Posted: Wed Jul 05, 2006 10:55 pm
|
Btw "G" is not a valid hex value so it wouldn't have worked regardless ;)
|
|
|
|
|
|
|
|
