Forums » Bugs
Binding commands to ^
I was trying to bind all the multilog commands to the shift+[number] keys since the F1-F6 keys are all set up for contrast, volume, etc on my iBook's keyboard and I'm too lazy to hit the fn+F1 since the buttons are spaced so far apart.
So, as I was binging, log1 was bound to !, log2 to @, log3 to #, log4 to $, and log5 to %.
But when I tried binding log6 to ^ nothing happenned. It just acted like I never typed /bind ^ log6 and when I hit ^ nothing happenned. I bound it to 6 (/bind 6 log6) and it worked fine. When I tried binding other commands like /hudmode to ^ they didn't work either. Why is this?
So, as I was binging, log1 was bound to !, log2 to @, log3 to #, log4 to $, and log5 to %.
But when I tried binding log6 to ^ nothing happenned. It just acted like I never typed /bind ^ log6 and when I hit ^ nothing happenned. I bound it to 6 (/bind 6 log6) and it worked fine. When I tried binding other commands like /hudmode to ^ they didn't work either. Why is this?
you can type ^ normally, in chat for example?
if you type /bind ^ what do you see?
it should tell you what is bound to that key.
if you type /bind ^ what do you see?
it should tell you what is bound to that key.
I see it normally in chat.
When /bind ^ is typed it puts up a list of all commands as if we just typed /bind.
Acts like the ^ character doesn't exist, yet shows up in the console and the chat.
When /bind ^ is typed it puts up a list of all commands as if we just typed /bind.
Acts like the ^ character doesn't exist, yet shows up in the console and the chat.
Huh very strange.
Try surrounding the ^ with quotes and see what happens.
You can also try adding the bind directly into your wgaf.cfg file.
Try surrounding the ^ with quotes and see what happens.
You can also try adding the bind directly into your wgaf.cfg file.
Surrounding ^ with quotes (/bind "^" alias) works just fine. It's odd that ^ isn't able to be bound directly, however.
Yeah that is very strange.
I'll test it here and see what's up with that.
I'll test it here and see what's up with that.
Heh yeah lex was absorbing the ^ char if it isn't surrounded by quotes.
It'll be fixed in the next release.
It'll be fixed in the next release.
Another chat bug - If I enter a message just as a new sector starts to load, the message is sent, but I cannot see it in my log or onscreen.
Yeah that's a known one. It's a server-side problem.
Is it being used as an escape character...?
No idea. I can't find anything in the lex & yacc book about it. Maybe it is. I just explicitly check for that character now.