Aliases and keybinds

[Xeno]

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 : ÒÅÓÉÓÔÁÎÃÅ ÉÓ ÆÕÔÉÌÅ =)"

=)

Nice one. I added it to the page but I changed it a little so that instead of having two keys, there is only one that toggles the effects on and off (with an echo message to let you know which one).

I liked the message too, but I don't know how much use of it beginners will get

[esteel]

You said on your page:

There's no point in including health/armor/weapon info in messages that aren't about you, e.g.:

The information is indeed not really needed but as long as Nexuiz does not have a team-overlay (like in quake3/4) that shows the health- and armor-status, weapon and location of your teammates it can be helpful to gather that information from those messages.
But on the other hand i was the one saying your messages are too long.. hehe.. its easy to copy/paste that info part if people think its useful

[Xeno]

You said on your page:

There's no point in including health/armor/weapon info in messages that aren't about you, e.g.:

The information is indeed not really needed but as long as Nexuiz does not have a team-overlay (like in quake3/4) that shows the health- and armor-status, weapon and location of your teammates it can be helpful to gather that information from those messages.
But on the other hand i was the one saying your messages are too long.. hehe.. its easy to copy/paste that info part if people think its useful

Just to make it clear, what I meant is that when you send a message such as "get out flag" to other members of the team, they don't really gain anything from knowing how much health etc you have. If you send a message like "I have the flag" (which is about you), then it is worth noting how much health etc you have so that they could head towards your location in anticipation of your death or need for help. I include health data (which btw I tweaked to make sure that it breaks up nicely on different lines consistently) on all commands which relate to what I'm doing (got the flag, heading to enemy base, defending, chasing enemy flag carrier, defending flag carrier, need help) but not messages to other people (defend, get their flag, get our flag).

I also just set the info part to a variable ($cStats) which makes it easer to include in all relevant messages.




On a side note, my version of the jump & moveup key can act a bit strangely if you get a weird frame rate (due to the "wait" command)... although it normally works fine, I keep a toggle key somewhere on the keyboard, just in case.

[ZWERG]

My communication script (at the moment CTF messages only) looks like this:

Code: Select all

// unbind keypad keys
alias unbind_keypad "unbind KP_0; unbind KP_1; unbind KP_2; unbind KP_3; unbind KP_4; unbind KP_5; unbind KP_6; unbind KP_7; unbind KP_8; unbind KP_9"
unbind_keypad

// define team messages
alias team_off_playing         "comm_mode_off; say_team I'm playing offense"
alias team_off_ready            "comm_mode_off; say_team >^6OFF^7< ready at [%l]"
alias team_off_down               "comm_mode_off; say_team >^6OFF^7< lost enemy flag at [%d]"
alias team_off_low_health      "comm_mode_off; say_team >^6OFF^7< low on health/armor [^1%h^7/^1%a^7]"
alias team_off_low_ammo         "comm_mode_off; say_team >^6OFF^7< low on ammo [NEED: ^2%W^7]"
alias team_off_need_gun         "comm_mode_off; say_team >^6OFF^7< need gun [HAVE: ^2%w^7]"

alias team_def_playing      "comm_mode_off; say_team I'm playing defense"
alias team_def_ready            "comm_mode_off; say_team >^5DEF^7< on position [%l]"
alias team_def_down               "comm_mode_off; say_team >^5DEF^7< lost position [%d]"
alias team_def_low_health      "comm_mode_off; say_team >^5DEF^7< low on health/armor [^1%h^7/^1%a^7], leaving position"
alias team_def_low_ammo         "comm_mode_off; say_team >^5DEF^7< low on ammo [NEED: ^2%W^7], leaving position"
alias team_def_need_gun         "comm_mode_off; say_team >^5DEF^7< need gun [HAVE: ^2%w^7], leaving position"

// comm mode level 2 aliases
alias team_off "echo 1....: lost flag...........; bind KP_1 team_off_down; echo 2....: ready...............; bind KP_2 team_off_ready; echo 3....: playing offense.....; bind KP_3 playing; bind KP_3 team_off_playing; echo 4/5/6: need health/ammo/gun; bind KP_4 team_off_low_health; bind KP_5 team_off_low_ammo; bind KP_6 team_off_need_gun"
alias team_def "echo 1....: lost position.......; bind KP_1 team_def_down; echo 2....: on position.........; bind KP_2 team_def_ready; echo 3....: playing defense.....; bind KP_3 playing; bind KP_3 team_def_playing; echo 4/5/6: need health/ammo/gun; bind KP_4 team_def_low_health; bind KP_5 team_def_low_ammo; bind KP_6 team_def_need_gun"

// comm mode level 1 aliases
alias comm_mode_on "alias comm_mode_toggle comm_mode_off; unbind_keypad; echo; echo; echo 1: OFFENSE; bind KP_1 team_off; echo 2: DEFENSE; bind KP_2 team_def"
alias comm_mode_off "alias comm_mode_toggle comm_mode_on; unbind_keypad; echo comm mode OFF"
alias comm_mode_toggle "comm_mode_on"

// comm mode related key bindings
bind "m" "comm_mode_toggle"


It's similar to esteel's script but uses a system like that of Wing Commander and similar games instead of a toggle: When you press "m" you'll get a menu
to choose between offense and defense messages and in the next sub-menu you can choose the message itself. E.g. if you press "m" "KP_1" "KP_1" it's the
message ">OFF< lost flag at [%d]".

The strings >OFF<, >DEF<, health/armor and items are colored. The locations are already colored with red/blue on some maps.

In addition I have bound time-critical messages to easily-accessible keys:

Code: Select all

bind "t" "say_team >^6OFF^7< lost enemy flag at [%d]"
bind "g" "say_team >^5DEF^7< lost position [%d]"
bind "CTRL" "say_team grab item [^2%x^7] at [%y]"


And some important messages like "ACK" and "NEGATIVE" are still missing.

[esteel]

The message menu is a nice idea, all the binds easily available but the switch is also good as one does need to press only one key to send a message. And switching roles should not happen that often so i think its faster

[esteel]

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"

Hmm the problem with that alias is the general movment is a bit crippled. Nexuiz (similar to quake) allows one to gain speed when jumping. The easiest way for keep jumping is to press +jump SOMETIME before actually landing, so you will jump again the moment you touch the ground. The exact timing does not matter though. With your alias one has to press the button very very shortly before touching the ground because of the -jump. I think being able to swim a bit faster is not worth to loose the easy jumping..

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"

With Nexuiz 1.5 or newer you could also use this:
bind "uparrow" "toggle cl_decals; echo cl_decals $cl_decals; toggle r_shadow_realtime_dlight; echo r_shadow_realtime_dlight $r_shadow_realtime_dlight"
pressing uparrow with enable or disable the features and also print their new values

I also kept thinking about the say_team binds i have. I came to the conclussion that its a good idea to change the binds from using (h:%h a:%a w:%w l:%l) to (l:%l h:%h a:%a w:%w). So that one will see your current location right after the message, then your health, armor and weapon last. For most if not even all messages its more important to know WHERE then the rest.. if someone says 'attacking' its good to know where, if health, armor are low or equipped with a bad weapon he should reconsider, but if you know where he is attacking you might help him. Same for 'defending' and 'need help', you need to know WHERE though if he has low health you should try to move faster to his position. For 'incoming', and 'took item' you also just want to know WHERE. 'quad', 'negative' all that info not that that important but as i mentioned earlier it can be interesting to know the other stuff thats why i still keep them

[Urmel]

for all the confused ppl: esteel means WHERE

so sorry, coudlnt hold aback

[esteel]

Oh yeah you are right.. guess i need to prove read it better next time.. even copied the text over into the 'team communication' thread

[Xeno]

http://alientrap.org/forum/viewtopic.php?t=1090

Adopt that colour scheme and the order of the info becomes mostly irrelevant. Have a look at my new suggestions and let me know what you think. I really want to get a semi-standard team message scheme going.

[esteel]

Code: Select all

bind "kp_minus" "freeview"
bind "kp_multiply" "demoview"
alias "+freeview" "set viewsize_backup $viewsize; set viewsize 120; set crosshair_backup $crosshair; set crosshair 0; set con_notify_backup $con_notify; set con_notify 0; set r_drawviewmodel_backup $r_drawviewmodel; set r_drawviewmodel 0; set showtime_backup $showtime; set showtime 0; set showfps_backup $showfps; set showfps 0; alias freeview -freeview"
alias "-freeview" "set viewsize $viewsize_backup; set crosshair $crosshair_backup; set con_notify $con_notify_backup; set r_drawviewmodel $r_drawviewmodel_backup; set showtime $showtime_backup; set showfps $showfps_backup; alias freeview +freeview"
alias "freeview" "+freeview"

alias "+demoview" "set viewsize_backup $viewsize; set viewsize 100; set crosshair_backup $crosshair; set crosshair 1; set con_notify_backup $con_notify; set con_notify 0; set r_drawviewmodel_backup $r_drawviewmodel; set r_drawviewmodel 1; set showtime_backup $showtime; set showtime 0; set showfps_backup $showfps; set showfps 0; set fov_backup $fov; set fov 90; alias demoview -demoview"
alias "-demoview" "set viewsize $viewsize_backup; set crosshair $crosshair_backup; set con_notify $con_notify_backup; set r_drawviewmodel $r_drawviewmodel_backup; set showtime $showtime_backup; set showfps $showfps_backup; set fov $fov_backup; alias demoview +demoview"
alias "demoview" "+demoview"

The first tries to hide everything to give you a nice view of the current scene, the second shows default fov, hud, weapon, crosshair. Press twice to restore 'your' settings again.