This small guide should help the people that didnt have a big knowledge about scripting and want to get a bit into it. Scripting can give you some advantages in the game but mostly it will make the game much more comfortable for you and will get you the highest performance possible.

Basics

First of all you should read through the basics of the bindigs etc. Basic informations about scripting you'll find HERE

Autoexec - The autoexec doesnt exactly work like explained in the links aboth. There are two folders were ETQW loads autoexec files on start up. One folder is C:/Documents and Settings/YourName/My Documents/idsoftware/Enemy Territory Quake Wars/base und C:/Documents and Settings/YourName/My Documents/idsoftware/Enemy Territory Quake Wars/sdnet/Accountname/base. The files are loaded in following order

execing 'etqwconfig.cfg' execing 'localization/english/defaultbinds.cfg' execing 'etqwbinds.cfg' execing 'autoexec.cfg' execing C:/Documents and Settings/YourNameMy Documents/id Software/Enemy Territory - Quake Wars/sdnet/AccountName/base/profile.cfg execing 'localization/english/defaultbinds.cfg' execing C:/Documents and Settings/YourNameMy Documents/iid Software/Enemy Territory - Quake Wars/sdnet/AccountName/base/bindings.cfg execing C:/Documents and Settings/YourNameMy Documents/iid Software/Enemy Territory - Quake Wars/sdnet/AccountName/base/autoexec.cfg

That means that all settings that you put in the autoexec.cfg in the /base folder can be overwrited through your profil confifgs in the sdnet/AccountName/base folder. Because of that you always should put the autoexec.cfg file into the /sdnet/AccountName/base folder but only put one command in it, exec 'myconfig.cfg' or somethings similar. The file 'myconfig.cfg' you put into the normal /base and put all the settings and binds in there. The reason for using the 'myconfig.cfg' file in that folder is that, if you're using several cfg files and you exec them, ETQW will search for them in the /base folder where the 'myconfig.cfg' is located and not where you exec the file for example in your 'autoexec.cfg'.

  Enable console - Usually you need to open the console throug CTRL+ALT+~. With the setting to enable the console you can open the console by simply hitting ~.

[config] seta com_allowconsole "1"

Use ALT+TAB - ETQW doesnt allow to switch back to window without changing some CVars. If you change the value from com_useFastVidRestart to 1 you can use ATL+ENTER instead of ALT+TAB. If you really want to use ALT+TAB you also need to change the value of win_notaskkeys to 1.

[config] seta com_useFastVidRestart "1" [config] seta win_notaskkeys "0"

Adjusting the brightness - Some maps are in general a bit darker or there are some places indoor that are really dark. If you adjust slightly your brightness it wont make a big difference on normal spots but will give you an advantage on dark maps and locations. Addiotionaly to the brightness you also can increase the gamma value slightly to make everything brighter.

[config] seta r_brightness "1.25" [config] seta r_gamma "1.1"

Change of FOV - The default value of the FieldOfView is 90°, not the greatest setting though. If you increase the FOV to 110 it will be a big advantage after a short time. Dont get confused if you enter a vehicle. Before the patch 1.4 there was a bug when you entered the titan. That was solved with a FOV lock inside vehicles.

[config] seta g_fov "110"

LagOMeter - The LagOMeter is a quite usefull tool that shows you all lags and their duration you're having on a server. This can help you optimising your computer performance. You should bind a key to the LagOMeter toggle, so you are able to switch it on or off.

[config] bind "Key" "toggle net_clientlagometer 0 1"

 
Show FPS - You can show your frames per second at the right top corner. Also that can help you to get the highest performance out of your system. You should bind a toggle to that too.

[config] bind "Key" "toggle com_showfps 0 1" - Keytoggle [config] seta com_showfps "1" - permanent Display

Skip intro - After some time of playing the game and starting it you'll surely have enough of skipping the intro manually. The config gives you the possibility to skip the intro by default.

[config] seta g_skipintro "1"

Chose default spawn - Usually ETQW automaticly chose the spawnpoint nearest to the action but if you once took another spawn you need to manually chose again the best. By binding the default spawn to a key you can easily spawn on the best spot without opening the limbomenu.

[config] bind "Key" "clientDefaultSpawn ; addChatLine 'Default Spawn Selected'"

Selfkill - To respawn really fast or to avoid getting revived you can bin selfkill to a key.

[config] bind "Key'" "kill; addChatLine 'Respawn'"

 

Advancrd

Basics were some general settings which are usefull for everybody and doesnt need much testing. The advanced scripting takes more time to find the best that suites you.

FPS Tuning - Already enough threads talked about that but it cant be missing in my guide. Usually ETQW is locked to 30 FPS but with some changes in the settings you can get much more FPS.

[config] seta com_unlockFPS "1" - 30 Disable 30 FPS lock [config] seta com_unlock_maxFPS "90" - Locks FPS to 90 FPS. You need to figure out whats the best for you. The max value you should be stabil and not bouncing around. [config] seta com_unlock_timingMethod "1" - 2 is bound to 30 FPS, 1 is a multiple of 30 und 0 is totaly unlocked from the FPS. I recommend 0 or 1 because for 2 you really need many FPS else you'll get a performance drop.

Ensure your VRAM is being used 100% - Tweak this to fit the VRAM on your video card.

[config] seta com_videoRam "256" - Exchange 256 with your graphics card RAM such as 512MB or 768MB.

Individualization

You should individualize your keys for every class and also for the vehicles. That will make you much flexible. With the context bindings you're able to make individual binds for every class and also every single vehicle.

 Vehicle controls - The vehicle controls can be very important. Bindings for example the decoys to a mouse key can save your live a few times. I have for example on the right mouse key the seat switch bind and ond the fourth mouse key I have the decoys. Works fine for me. Theoreticly you can make binds for every single vehicle for example for the bumblebee (seta g_bind_context_bumblebee "bumblebee")

[config] bind "MOUSE2" ""_vehiclePosition"" "" "vehicle" - Seat switching [config] bind "MOUSE4" "_weapon0" "" "vehicle" - Decoys g_bind_context_badger "vehicle" g_bind_context_bumblebee "vehicle" g_bind_context_desecrator "vehicle" g_bind_context_goliath "vehicle" g_bind_context_hog "vehicle" g_bind_context_husky "vehicle" g_bind_context_icarus "vehicle" g_bind_context_mcp "vehicle" g_bind_context_platypus "vehicle" g_bind_context_titan "vehicle" g_bind_context_trojan "vehicle"

 Flyers - You can also individualize your keybindings for the flyers. Ususally the flyers are bound to the vehicle controls but with changing the context bind you can bind the flyers to a seperate class and make seperate binds. Important functions for the flyers are _speed - standing still in midair and _tophat - Overhead view

[config] seta g_bind_context_anansi "flyers" [config] seta g_bind_context_hornet "flyers" [config] bind "MOUSE2" "_weapnext" "" "flyers" - Better weapon switch

Class specific binds - I recommend that you make special keybinds for every class. Most mices have a fourth mouse key and this can be very important for class specific binds. With the "context" in the binds you can handle the clasbinds. For CovertOps/Infiltrator is _activate usefull to bind on the mouse cause its a good scope zoom and you can walk better while hacking. Here one example of how to make a class bind. You should find out the rest on your own.

[config] bind "MOUSE4" "_activate" "" "covertops" g_class_context_aggressor "aggressor" g_class_context_technician "technician" g_class_context_constructor "constructor" g_class_context_oppressor "oppressor" g_class_context_infiltrator "infiltrator" g_class_context_soldier "soldier" g_class_context_medic "medic" g_class_context_engineer "engineer" g_class_context_fieldops "fieldops" g_class_context_covertops "covertops"

 

HUD

The HUD is pretty overloaded with all the menus and stuff. Some things can easily be disabled without missing them but also with changing the opacity a bit you can make the the HUD much compacter.

Advanced HUD - Since patch 1.4 you have the option to enable/disable the advanced HUD. Only change I recognized yet is that the playernames of the players in your vehicle are shown permanently

[config] seta g_advancedHud "1"

Votes - The votes can be annoying sometimes. There are two options to handle it. First you can change the opacity and second you can enable that the vote disappeares after you voted.

[config] seta gui_voteAlpha "0.5" [config] seta g_voteKeepVote "0"

Waypoints - You can individualize the waypoints pretty much. You can set different size, opacity, view distance etc.

[config] seta g_waypointAlphaScale "0.5" [config] seta g_waypointDistanceMax "3084" [config] seta g_waypointDistanceMin "16" [config] seta g_waypointSizeMax "15" [config] seta g_waypointSizeMin "10"

Icons - In ETQW everything has icons over it, even the unused vehicles. Make them smaller or disable them makes it less annoying.

[config] seta g_playerIconAlphaScale "0.5" [config] seta g_playerIconSize "10" [config] seta g_drawVehicleIcons "0" - Disable the vehicle icons

Mienes - Since patch 1.4 the mines are nerfed. You now get a trigger warning and the mines have green or red dots on it. If you dont want to disable the dots you can make the dots smaller seta g_mineIconSize or/and change the opacity g_mineIconAlphaScale.

[config] seta g_drawMineIcons "0" [config] seta g_mineTriggerWarning "0"

Objectives - There are a few menus about the objectives. I recommend to change the opacity slightly to make the HUD less heavy. I dont suggest to disable them completly

[config] seta gui_objectiveListAlpha "0.8" [config] seta gui_objectiveStatusAlpha "0.8"

Crosshair - The crosshair is quite important. You should make the crosshair the smallest you. Less is more. No one really needs to know the spreading.

[config] seta gui_crosshairColor "1 1 1 1" [config] seta gui_crosshairSpreadScale "0" [config] seta gui_crosshairGrenadeAlpha "0.286585" [config] seta gui_crosshairStatsAlpha "0" [config] seta gui_crosshairSpreadAlpha "0" [config] seta gui_crosshairAlpha "0.5"

Vehicles - You can disable the vehicle cockpit completly. You can also change the opacity of the direction indicator and of the vehicle HUD.

[config] seta g_showVehicleCockpits "0" [config] seta gui_vehicleDirectionAlpha "0.5" [config] seta gui_vehicleAlpha "0.8"

Misc - Misc says all. There are some more settings but they arent wearth a submenu. e.g. CommandMap opacity, tooltips, decals, fireteamlist, chat, personalBest, fraglist und respawntext.

[config] seta gui_obitAlpha "1" - Opacity of the fraglist [config] seta gui_commandMapAlpha "1" - Opacity of the Commandmap [config] seta gui_fireTeamAlpha "0.8" - Opacity ot the Fireteamlist [config] seta gui_chatAlpha "1" - Opacity of the Chats [config] seta gui_personalBestsAlpha "0" - Opacity of the personalbest list (disabling doesn't work yet because of a bug) [config] seta gui_showRespawnText "0" - disable respawntext [config] seta g_tooltipTimeScale "0" - disable tooltips [config] seta g_decals "0" - Disable decals such as bullet holes

 

Scripts

Why making scripts that already exists. Here a list of some usefull scripts but there are a lot more.

Ever wanted to change the channel you were submitting your VOIP, but don't want 3 different buttons? Here's my config, which lets you switch it by pressing ALT-1, ALT-2, or ALT-3. My bind to talk is B, so you'll need to switch that to match your bind key.

bind "1" "bind b _fireteamvoice; addchatline '^1Voice bind set to ^2Fireteam only'" "alt" "" bind "2" "bind b _teamvoice; addchatline '^1Voice bind set to ^2Team only'" "alt" "" bind "3" "bind b _voice; addchatline '^1Voice bind set to ^2Global'" "alt" ""

 

Quick Fireteam - Play with the same bunch of people usually? Want to quickly toss them all an invite to a new fireteam, with all settings & it's name ready to go? Here's the script for you.
 
Class Selection - The scripts are a bit to big to post the here. Here are some examples
bind F1 "fireteam disband;fireteam create; fireteam name '#FIRETEAM NAME'; fireteam private; fireteam invite #NAME1; fireteam invite #NAME2; addchatline '^8Fireteam ^3Created'" "alt" "default"
VSays toggle by Ralle

// cough Toggle seta saycough "clientquickchat quickchat/global/taunts/cough; bind HOME $sayoops" seta sayoops "clientquickchat quickchat/global/taunts/oops; bind HOME $sayohdear" seta sayohdear "clientquickchat quickchat/global/taunts/ohdear; bind HOME $saycough" bind "HOME" "vstr saycough" // awkward Toggle seta sayawk "clientquickchat quickchat/global/taunts/awkward; bind PGUP $sayawy" seta sayawy "clientquickchat quickchat/global/taunts/awyeahohno; bind PGUP $sayawn" seta sayawn "clientquickchat quickchat/global/taunts/awnoheyyeah; bind PGUP $sayawk" bind "PGUP" "vstr sayawk" // owned Toggle seta sayown "clientquickchat quickchat/global/taunts/owned; bind END $sayhurt" seta sayhurt "clientquickchat quickchat/global/taunts/thathurt; bind END $sayhadto" seta sayhadto "clientquickchat quickchat/global/taunts/thathadtohurt; bind END $sayown" bind "END" "vstr sayown" // meh Toggle seta saymeh "clientquickchat quickchat/global/taunts/meh; bind PGDN $sayihad" seta sayihad "clientquickchat quickchat/global/taunts/ihadworse; bind PGDN $saymeh" bind "PGDN" "vstr saymeh"

Competitive

Here are some tweaks of the Pro's

Increase view distance - There are two settings to increase your view dinstance.

[config] seta image_lodbias "-1" [config] seta r_visdistmult "1.2"

Rendering - Here are some tips of things you can disable for more performance

[config] seta r_skipBump "1" - Disables the bump while walking [config] seta r_skipSpecular "1" [config] seta r_megaDrawMethod "3" - 3 more performance, less nicegraphic [config] seta r_shadows "0" - Disables all shadows [config] seta r_skipstuff "1" - Disables gras etc. [config] seta r_shaderQuality "0" - Shader quality [config] seta r_detailTexture "0" - Detaillevel textures [config] seta r_detailFade "0" - Detaillevel fades [config] seta r_softParticles "0" - Disables SoftParticles [config] seta r_useThreadedRenderer "2" - Rendering unlocked from the FPS

Link: Questions and Feedback Thread