caps


(={Pha}=Vile) #1

I can’t get caps to show up in ET

in config:
bind a “team r 1; echo You will respawn as a ^3Medic; say_team ^0<- -=>)} ^7Going ^7Medic ^0{(<=- ->”

in game:
<- -=>)} going medic {(<=- ->

same happen with names:
bind 0 ^0DrAgOnFlY

in game it reads:
dragonfly


(Kendle) #2

Try this:-

set med-message “say_team ^0<- -=>)} ^7Going ^7Medic ^0{(<=- ->”
bind a “team r 1; echo You will respawn as a ^3Medic; vstr med-message”

Don’t ask me why it works, but it does. :slight_smile:


(mouse) #3

maybe you should loose the brackets and stuff and try that first, maybe that is interrupting the code.


(=DaRk=CrAzY-NuTTeR) #4

nope, brackets are there if u using and gaps and spaces, if it gets a gab it thinks its finished and would only say ‘<- -=>)}’


(Kendle) #5

The brackets mean nothing, they’re just characters to display and have no effect on how the command works. Gaps are included as long as the command is enclosed in quotes.

For example:-

say_team Hello World would display hello

say_team “Hello World” would display hello world

say_team )[{{)] Hello World [(}}[( would display )[{{)]

say_team “)[{{)] Hello World [(}}[(” would display )[{{)] hello world [(}}[(

set msg “say_team )[{{)] Hello World [(}}[(”
vstr msg
would display )[{{)] Hello World [(}}[(

You just need to put the say_team command in it’s own variable and execute the variable with vstr in order to preserve case.


(mouse) #6

Sorry i meant the []{}-= thingy’s, I know that using <o/ in my namescript didnt work because the / works as a comment sign (correct?). Thought that maybe one of those other thingy’s could maybe also have that problem.