Oooh, yes, that is my fault. I accidentally set the max-characters to 1.
Till then, you can use the console to change your name.
Will be fixed in the next version!
Oooh, yes, that is my fault. I accidentally set the max-characters to 1.
H-h-h-h-how on earth?
Btw, i would like to request something as well: Since tremulous, ^[number] characters also count to the character limit. In other words, i can do a rainbow of colours, but my name would be very short (limited). Whereas, a completely blank name can get into the scores side.
@dwarf:
You don't need to do /seta name [name]. Just do /name [name].
Actually, i need to ask, whats the difference between seta and set? Does set no write to autogen.cfg or something like that?
@ViruS: i don't exactly know witch one does permanently write to the cfg file and witch command only sets the variable for the session beeing. But as i used the seta command in the past and my name is colored since then, i guess its the "seta" command to write out variables to your cfg file. Although to be 100% sure about that, i guess i'll have to ask google ....but:
... <- me lazy as hell ;)
I googled it. According to http://quakeforge.net/doxygen/cvars.html
seta is more permanent. Apart from that, they're both the same. For those who cbf reading the article:
Cvar related commands.
<cvar> [value]
Display the current value of the specified cvar. If value is given, set the cvar to value. Does not create a new cvar.
set <cvar> <value>
Set the specified cvar to the specified value. If the cvar does not already exist, a new cvar will be created.
seta <cvar> <value>
Set the specified cvar to the specified value. If the cvar does not already exist, a new cvar will be created. Sets the cvar's archive flag so it will be automatically saved to config.cfg by the clients.
setrom <cvar> <value>
Set the specified cvar to the specified value. If the cvar does not already exist, a new cvar will be created. Sets the cvar's read-only flag so it can no longer be modified in any way (not even by reset or resetall).
toggle <cvar>
Treat the cvar as a boolean value, changing it from off to on, or on to off. Any non-zero integer value is considered to be on, while zero and any string that parses as zero (does not start with a non-zero number) will be treated as off. The new value will always be either one (1) or zero (0).
Note:
values smaller than 1 will be treated as off.