Aliases and keybinds

[Xeno]

Does anyone have any good aliases or keybinds that they want to share? I want to add them to a section on a page that I created to collect useful info and functions.

Btw, have a look at the font converter and the suggestions for teamsay message color schemes to make them easier to read.

Xeno's Nexuiz Config Page

[ai]

IMO colored text messages (with spaces, weird chars and whatnot) is lot more diffucult to see than the normal white. That's cause I'm accustomed to the white text and can quickly read it but even if it's two words with colored text it gets harder. Maybe cause people use caps letters to that too and I usually see that nothing more than spam things so I don't even bother to read it most of the time

Just how I was brought up :p It would be easier to just seperate it from simple chars like , >> <<, " ", // etc. Example: "Attacking!", "Defending!", "Enemy got our flag!", "Flag at >> 'Whatever position (underground tunnel)'", "Friendly flag incoming from > 'Some other position'", "Incoming enemies!". Something like that.

[esteel]

Hi there.. have seen you online, hope you enjoy the forum

Well i use those:
Only useful in water and the only map with enough water is gone now. You can swim down and duck while doing so with the same key.

Code: Select all

alias "+cmd" "+crouch; +movedown"
alias "-cmd" "-crouch; -movedown"

Useful info: +moveup will make you swim faster up in water then +jump. Using both together (with a opposite alias) seems to trigger +jump first so its not as fast as just +moveup.

Fast zoom:

Code: Select all

alias "+zoom" "set fov 36; set sensitivity 2.083"
alias "-zoom" "set fov 110; set sensitivity 6.25"

The idea with colored messages is good as i already mentioned in the team communication thread but its HARD to find colors people like and agree on.. for example i would use colors closer to the pickup items.. this means the health info would be red, the armor green. No idea about the weapons and location. In general darkblue is hard to read on dark backgrounds.
Also i think its good to give different message types different colors.. Warnings (help, incoming) should be red, info (attacking, defending) yellow, maybe the quad soon message should be cyan (classic color of the quake quad damage and also the nex powerup).
You see two of two people already can't agree on colors Thats why i did just mention them in my post but did not make them colored..

If you use the same colors for all messages they should be shorter then what you have right now. That makes it easier and faster to read them. But the line breakes might get different then.. I changed my messages a few times and right now all of them have 2 words at most while the first word is different for each message. Sure its way easier to 'get' your messages put i think they are more of a distraction because they are quite long. Kinda extreme are people that do not like my long versions of 'gg' and 'gl&hf' because they are long and do not match the learned pattern. Your long messages have the same basic problem but before or after the game were timing does not matter its ok and i also think it shows more respect to write whole words in those two cases
On the topic of easy reading: Lowercase is easier to read then upper case. So using the 'cool' or 'lcd' font makes it harder to read (and also to edit) then the normal font in lowercase.

%x does not use map location, %d does. %x just tells the name of the item. Guess thats an typo.

[Xeno]

Well i use those:
Only useful in water and the only map with enough water is gone now. You can swim down and duck while doing so with the same key.

Code: Select all

alias "+cmd" "+crouch; +movedown"
alias "-cmd" "-crouch; -movedown"

Useful info: +moveup will make you swim faster up in water then +jump. Using both together (with a opposite alias) seems to trigger +jump first so its not as fast as just +moveup.

Fast zoom:

Code: Select all

alias "+zoom" "set fov 36; set sensitivity 2.083"
alias "-zoom" "set fov 110; set sensitivity 6.25"

Thanks, I added them to the page.

The idea with colored messages is good as i already mentioned in the team communication thread but its HARD to find colors people like and agree on.. for example i would use colors closer to the pickup items.. this means the health info would be red, the armor green. No idea about the weapons and location. In general darkblue is hard to read on dark backgrounds.
Also i think its good to give different message types different colors.. Warnings (help, incoming) should be red, info (attacking, defending) yellow, maybe the quad soon message should be cyan (classic color of the quake quad damage and also the nex powerup).
You see two of two people already can't agree on colors Thats why i did just mention them in my post but did not make them colored..

I went with green for health/hp just because I'm used to it from various games and because it stands out a bit more than red, especially since team_say will have red parentheses when you're on the red team. I chose yellow for armor because the HUD shows your armor in yellow. I used cyan for all the messages because it shows up well in general. I see the rationale behind using different colors for different messages though... hmmm. Like I said, I haven't been playing long enough and nobody else uses colored messages so I haven't actually had any experience reading other people's messages in color and seeing which ones are clearer. I used magenta for the location because it stands out too and it's more important than the weapon that you're using. I really only threw in the weapon in blue for fun.

If you use the same colors for all messages they should be shorter then what you have right now. That makes it easier and faster to read them. But the line breakes might get different then.. I changed my messages a few times and right now all of them have 2 words at most while the first word is different for each message. Sure its way easier to 'get' your messages put i think they are more of a distraction because they are quite long. Kinda extreme are people that do not like my long versions of 'gg' and 'gl&hf' because they are long and do not match the learned pattern. Your long messages have the same basic problem but before or after the game were timing does not matter its ok and i also think it shows more respect to write whole words in those two cases
On the topic of easy reading: Lowercase is easier to read then upper case. So using the 'cool' or 'lcd' font makes it harder to read (and also to edit) then the normal font in lowercase.

I thought that because the messages are color-coded and break up nicely, it would be easier to read. All messages where I include extra data (health, armor, etc) follow the same format... the main message is directly at the top. If you need to know more, you can scan the rest of the message (which should be fast with the color coding). Like I said though, I'm still a noob and I haven't seen any colored messages so I don't know how practical they are. Regarding the font, I'm not sure what's easiest to read (although both of you have said lowercase already... although that might just be due to habit). I used the "cool" font because I had written the converter and felt that I should make use of it

%x does not use map location, %d does. %x just tells the name of the item. Guess thats an typo.

Yep, I meant to write %d instead of %x... nice catch.

[Xeno]

Can you use mathematical operations in aliases at all?

E.g.
set fov_old fov;set fov_new fov_old/2.5
set sensitivity sensitivity-2

etc?

[esteel]

Not really prove but anyway: http://hubel.sfasu.edu/courseinfo/SL03/email_study.htm

The shape of a lower case word provides significant clues to the reader as to its identity, whereas a word in all capital letters has a destroyed shape (no ascenders or descenders), so the word appears to be rectangular (Williams, 2000). When unable to use previous experience and knowledge of word shapes, reading time slows as a result of slowed processing. Upper case type is read about 13 percent slower than lowercase type (Tinker, 1955 as cited in Williams).

Some others say uppercase is up to 20% slower to read..

The difficulty to find 'good' colors (and the portability into other games) stopped me from using them so far. Also i'm more of a purist and reading one word (the significant first word in my messages) should be ok regardless of its color Its really nice to see colored messages in demos but as almost anyone would use other colors i went with the simple uncolored version..

As far as i know you can't use math in aliases. You can just access the value of variables.

set oldfov $fov; set fov 180; set fov $oldfov

Well one could use aliases to get more chat messages.

alias "set_attack" "echo attacking messages active; alias toggle_msg set_defend; alias msg1 msg_attack1; alias msg2 msg_attack2; alias msg3 msg_attack3; alias msg4 msg_attack4; alias msg5 msg_attack5; alias msg6 msg_attack6; alias msg7 msg_attack7; alias msg8 msg_attack8; alias msg9 msg_attack9"
alias "set_defend" "echo defending messages active; alias toggle_msg set_misc; alias msg1 msg_defend1; alias msg2 msg_defend2; alias msg3 msg_defend3; alias msg4 msg_defend4; alias msg5 msg_defend5; alias msg6 msg_defend6; alias msg7 msg_defend7; alias msg8 msg_defend8; alias msg9 msg_defend9"
alias "set_misc" "echo misc messages active; alias toggle_msg set_attack; alias msg1 msg_misc1; alias msg2 msg_misc2; alias msg3 msg_misc3; alias msg4 msg_misc4; alias msg5 msg_misc5; alias msg6 msg_misc6; alias msg7 msg_misc7; alias msg8 msg_misc8; alias msg9 msg_misc9"
alias "toggle_msg" "set_attack"

alias "msg_attack1" "say_team attacking"
alias "msg_attack2" "say_team have flag"
alias "msg_attack3" "say_team need help attacking"
alias "msg_attack4" "say_team attack NOW"
alias "msg_attack5" "say_team regroup at base"
alias "msg_attack6" "say_team lost flag at %d"
alias "msg_attack7" "say_team someone protect me"
alias "msg_attack8" "say_team incoming"
alias "msg_attack9" "say_team incoming HIGH"

alias "msg_defend1" "say_team defending"
alias "msg_defend2" "say_team protecting flagcarrier"
alias "msg_defend3" "say_team need help defending"
alias "msg_defend4" "say_team need FUCKING HELP RIGHT NOW"
alias "msg_defend5" "say_team regroup at base"
alias "msg_defend6" "say_team flag was taken"
alias "msg_defend7" "say_team flag seen at %y"
alias "msg_defend8" "say_team need message "
alias "msg_defend9" "say_team need message "

alias "msg_misc1" "say_team item here"
alias "msg_misc2" "say_team quad soon"
alias "msg_misc3" "say_team took item"
alias "msg_misc4" "say_team need armor"
alias "msg_misc5" "say_team need health"
alias "msg_misc6" "say_team need weapon"
alias "msg_misc7" "say hi"
alias "msg_misc8" "say gl&hf: good luck n have fun"
alias "msg_misc9" "say gg: good game"

bind "1" "msg1"
bind "2" "msg2"
bind "3" "msg3"
bind "4" "msg4"
bind "5" "msg5"
bind "6" "msg6"
bind "7" "msg7"
bind "8" "msg8"
bind "9" "msg9"
bind "0" "toggle_msg"

You can use 0 to toggle through the messages and 1-9 to print the current messages..

[morfar]

Hello, I can share my zoom script. (But I never zoom, but other might like it ;P)

place this in your autoexec.cfg. If don't have autoexec.cfg - then create it.

Code: Select all

// zoom script
set fov_orginal $fov
set fov_zoomvalue 50
set fov_sensorginal $sensitivity
set fov_sens 1.2
alias "+fov_zoom" "fov $fov_zoomvalue ; sensitivity $fov_sens"
alias "-fov_zoom" "fov $fov_orginal ; sensitivity $fov_sensorginal"

alias zoom_toggle "zoom_on"
alias zoom_on "fov $fov_zoomvalue ; sensitivity $fov_sens ; alias zoom_toggle zoom_off"
alias zoom_off "fov $fov_orginal ; sensitivity $fov_sensorginal ; alias zoom_toggle zoom_on"

bind mouse3 "+fov_zoom" // zoomed in while pressing
bind x "zoom_toggle" // zoom toggle


You can of course change the binds in the script. You can customize the zoom strength with 'set fov_zoomvalue' and the zoom sensitivity with 'set fov_sens'.

[Xeno]

http://hubel.sfasu.edu/courseinfo/SL03/email_study.htm
Some others say uppercase is up to 20% slower to read..

I doubt that it really makes any noticeable difference when you're dealing with up to 4 words, plus you would quickly learn to recognize them after you've seen them a few times. I don't doubt that lowercase letters are better for lengthy writing but anyone who spams a novel in teamspeak will probably be ignored no matter what case it was written in

I don't mind either way really, I'm more for just getting people to use the messages to begin with, hopefully with some color scheme (not necessarily mine).

As far as i know you can't use math in aliases. You can just access the value of variables.

set oldfov $fov; set fov 180; set fov $oldfov

Well one could use aliases to get more chat messages.

I had the same idea but I would use a key to toggle between ctf and domination message binds, for example... unfortunately domination matches are few and far between (lack of maps I suspect, plus dom requires some level of team cooperation to be really fun).






Btw, I found a way to bind MOVEUP to jump so that it works in water:
alias +ascend "+jump;wait;-jump;+moveup"
alias -ascend "-jump; -moveup"

I don't think that the second -jump does anything but I just didn't remove it. Anyway, it seems to work exactly like the jump button for all practical purposes, plus you move up in water a lot faster... now we just need some maps with water on them.


Also, to anyone reading this, I overhauled my enhanced zoom function:
It now stores your current fov and sensitivity and restores them when not zooming (so that you don't have to set them in the file)
The last magnification is stored and set to default (so that you can use it the same way that most people seem to use their zoom aliases... statically)
I reduced the number of magnifications
I made it easier to configure
I added a toggle key

I also made a second enhanced zoom function that produces exactly the same magnification as the other one but without the zoom transition, which makes it faster.












Morfar, jag tycker om din Conanball Z gif. Jag skrattar varje gång jag ser den.

[morfar]

Morfar, jag tycker om din Conanball Z gif. Jag skrattar varje gång jag ser den.

[*HxC*Cuizinier]

I have this in my cuizi.cfg :

Code: Select all

bind "UPARROW" "dyndecon"
bind "DOWNARROW" "dyndecoff"

alias "dyndecon" "set cl_decals 1;set r_shadow_realtime_dlight 1"
alias "dyndecoff" "set cl_decals 0;set r_shadow_realtime_dlight 0"


I turn it on when there are < 6 players (1on1) and off else.
There are graphic options appear useful to me. (most in 1on1)

decals are the marks that leaves the weapons on the wall. can be usefull to know where you shoot or where the enemie shoot.

shadow_realtime_dlight is the light which surrounds the things sent. Usefull to see if a rocket will hurt you. other thing : you can see people who have the quad through the walls

the last one need much graphic resource it is for that reason I turn off it when they have too much players.
note : all other realtime effect disable.

But I think my best bind is :

Code: Select all

bind "j" "say ^0[^2ÐÇÐ^0]^2 : ÒÅÓÉÓÔÁÎÃÅ ÉÓ ÆÕÔÉÌÅ =)"

=)