I Can't Use Voicecomm In Commandermode!
MonsieurEvil
Join Date: 2002-01-22 Member: 4Members, Retired Developer, NS1 Playtester, Contributor
Join Date: 2002-01-22 Member: 4Members, Retired Developer, NS1 Playtester, Contributor
<div class="IPBDescription">Or other keyboard weirdness in CM</div> Commander mode uses a special set of hotkeys and other keyboard code in order to function properly. Due to some HL engine limits and NS interface design decisions, this means there are certain things you cannot and should not do when mapping keys:
1. Do not bind your voicecomm to a mousebutton - HL only supports this in certain configurations, none of which we will support. Use the default of 'CAPSLOCK' for best results (i.e. bind "capslock" "+voicerecord").
2. Do not custom bind your voicecomm or jump butons to one of the commander mode hotkeys - these are by default:
qwer
asdf
zxcv
If you wish to use one of these keys for jump, voicecomm, or something else, we suggest remapping the hotkeys via the hl config (advanced, page 2) menu, using scripts, or using aliases. Or remapping your custom keys, naturally.
Edit: corrected keys, thanks for the sharp eyes Rave
1. Do not bind your voicecomm to a mousebutton - HL only supports this in certain configurations, none of which we will support. Use the default of 'CAPSLOCK' for best results (i.e. bind "capslock" "+voicerecord").
2. Do not custom bind your voicecomm or jump butons to one of the commander mode hotkeys - these are by default:
qwer
asdf
zxcv
If you wish to use one of these keys for jump, voicecomm, or something else, we suggest remapping the hotkeys via the hl config (advanced, page 2) menu, using scripts, or using aliases. Or remapping your custom keys, naturally.
Edit: corrected keys, thanks for the sharp eyes Rave
This discussion has been closed.