 |
saet
Apprentice
Joined: 12 Jun 2006
Posts: 106
|
 Posted: Tue Jul 18, 2006 4:07 pm
[1.02] #PCOL
|
It acts exactly like #COLOR now, coloring the whole line. Tested on many strings.
|
|
|
|
|
acaykath
Wanderer
Joined: 03 Aug 2005
Posts: 84
|
Posted: Wed Jul 19, 2006 11:46 pm
|
It's not working for me at all. I know the triggers are running... but the pcol is not coloring anything.
ex:
#TRIGGER {Your clumsy * ({misses|bruises}) *.} {#PCOL {#FFFFFF %x1}}
It took me a whilt to even get it to accept the trigger since zMud didn't need {} for the #pcol. I have tried 0x $ # and making em strings, but the words always remain the default colour. Am I doing something wrong? |
|
|
|
|
saet
Apprentice
Joined: 12 Jun 2006
Posts: 106
|
Posted: Thu Jul 20, 2006 12:43 am
|
#PCOL 0xFFFFFF %x1
#PCOL "#FFFFFF" %x1
#PCOL "$FFFFFF" %x1
no {}'s. |
|
|
|
|
acaykath
Wanderer
Joined: 03 Aug 2005
Posts: 84
|
Posted: Thu Jul 20, 2006 12:52 am
|
Without the {}s I get a parse error when I try to create the trigger via the command line.Without them, it works but colors the whole line.
|
|
|
|
|
saet
Apprentice
Joined: 12 Jun 2006
Posts: 106
|
Posted: Thu Jul 20, 2006 1:04 am
|
I'm only getting the error when I do #FFFFFF without quotes.
The coloring of the whole line is a bug. |
|
|
|
|
acaykath
Wanderer
Joined: 03 Aug 2005
Posts: 84
|
Posted: Thu Jul 20, 2006 1:10 am
|
Ah, thats the way I wrote it in zMud, stupid quotes... everything is switched to 0x notation now... so it works via command line without errors
|
|
|
|
|
|
|
|
