Jump to content

Player Gaming Stats for =F|A= Servers


Wolf ET : Experienced Players - Enemy Territory

Recommended Posts

Some may need some scripts to improve their gameplay:






set Axis "team r 1 3 38;say_team ^1Spawn Axis; play sound/menu/select.wav; set AxisAllies vstr Allies"
set Allies "team b 1 8 37;say_team ^1Spawn Allies; play sound/menu/select.wav; set AxisAllies vstr Axis"
set AxisAllies "vstr Axis"
set afk1 "team s; set name EtplayerAFK; set nextstatus vstr afk2; Echo Current Status: ^1AFK; say ^1AFK"
set afk2 "set name Etplayer; set nextstatus vstr afk1; Echo Current Status: ^1Back; say ^1Back"
set nextstatus "vstr afk1"
set st "vstr statisticsall"
set statisticsall "vstr statistics"
set statistics "+topshots;+stats;set statisticsall vstr statistics2"
set statistics2 "-topshots;-stats;set statisticsall vstr statistics"
set sens "vstr sens0"
set sens0 "sensitivity 5; set sens vstr sens1; Echo Current Status: ^1sensitivity 5"
set sens1 "sensitivity 4.9; set sens vstr sens2; Echo Current Status: ^1sensitivity 4.9"
set sens2 "sensitivity 4.8; set sens vstr sens3; Echo Current Status: ^1sensitivity 4.8"
set sens3 "sensitivity 4.7; set sens vstr sens4; Echo Current Status: ^1sensitivity 4.7"
set sens4 "sensitivity 4.6; set sens vstr sens5; Echo Current Status: ^1sensitivity 4.6"
set sens5 "sensitivity 4.5; set sens vstr sens6; Echo Current Status: ^1sensitivity 4.5"
set sens6 "sensitivity 4.4; set sens vstr sens7; Echo Current Status: ^1sensitivity 4.4"
set sens7 "sensitivity 4.3; set sens vstr sens8; Echo Current Status: ^1sensitivity 4.3"
set sens8 "sensitivity 4.2; set sens vstr sens9; Echo Current Status: ^1sensitivity 4.2"
set sens9 "sensitivity 4.1; set sens vstr sens10; Echo Current Status: ^1sensitivity 4.1"
set sens10 "sensitivity 4; set sens vstr sens11; Echo Current Status: ^1sensitivity 4"
set sens11 "sensitivity 3.9; set sens vstr sens12; Echo Current Status: ^1sensitivity 3.9"
set sens12 "sensitivity 3.8; set sens vstr sens13; Echo Current Status: ^1sensitivity 3.8"
set sens13 "sensitivity 3.7; set sens vstr sens14; Echo Current Status: ^1sensitivity 3.7"
set sens14 "sensitivity 3.6; set sens vstr sens15; Echo Current Status: ^1sensitivity 3.6"
set sens15 "1sensitivity 3.5; set sens vstr sens16; Echo Current Status: ^1sensitivity 3.5"
set sens16 "sensitivity 3.4; set sens vstr sens17; Echo Current Status: ^1sensitivity 3.4"
set sens17 "sensitivity 3.3; set sens vstr sens18; Echo Current Status: ^1sensitivity 3.3"
set sens18 "sensitivity 3.2; set sens vstr sens19; Echo Current Status: ^1sensitivity 3.2"
set sens19 "sensitivity 3.1; set sens vstr sens20; Echo Current Status: ^1sensitivity 3.1"
set sens20 "sensitivity 3; set sens vstr sens0; Echo Current Status: ^1sensitivity 3"
set gamma "vstr gamma0"
set gamma0 "r_gamma 3; set gamma vstr gamma1; Echo Current Status: ^1gamma 3"
set gamma1 "r_gamma 2.9; set gamma vstr gamma2; Echo Current Status: ^1gamma 2.9"
set gamma2 "r_gamma 2.8; set gamma vstr gamma3; Echo Current Status: ^1gamma 2.8"
set gamma3 "r_gamma 2.7; set gamma vstr gamma4; Echo Current Status: ^1gamma 2.7"
set gamma4 "r_gamma 2.6; set gamma vstr gamma5; Echo Current Status: ^1gamma 2.6"
set gamma5 "r_gamma 2.5; set gamma vstr gamma6; Echo Current Status: ^1gamma 2.5"
set gamma6 "r_gamma 2.4; set gamma vstr gamma7; Echo Current Status: ^1gamma 2.4"
set gamma7 "r_gamma 2.3; set gamma vstr gamma8; Echo Current Status: ^1gamma 2.3"
set gamma8 "r_gamma 2.2; set gamma vstr gamma9; Echo Current Status: ^1gamma 2.2"
set gamma9 "r_gamma 2.1; set gamma vstr gamma10; Echo Current Status: ^1gamma 2.1"
set gamma10 "r_gamma 2; set gamma vstr gamma11; Echo Current Status: ^1gamma 2"
set gamma11 "r_gamma 1.9; set gamma vstr gamma12; Echo Current Status: ^1gamma 1.9"
set gamma12 "r_gamma 1.8; set gamma vstr gamma13; Echo Current Status: ^1gamma 1.8"
set gamma13 "r_gamma 1.7; set gamma vstr gamma14; Echo Current Status: ^1gamma 1.7"
set gamma14 "r_gamma 1.6; set gamma vstr gamma15; Echo Current Status: ^1gamma 1.6"
set gamma15 "r_gamma 1.5; set gamma vstr gamma16; Echo Current Status: ^1gamma 1.5"
set gamma16 "r_gamma 1.4; set gamma vstr gamma17; Echo Current Status: ^1gamma 1.4"
set gamma17 "r_gamma 1.3; set gamma vstr gamma0; Echo Current Status: ^1gamma 1.3"
set sound "vstr sound0"
set sound0 "s_volume 0.9; set sound vstr sound1; Echo Current Status: ^1volume 0.9"
set sound1 "s_volume 0.8; set sound vstr sound2; Echo Current Status: ^1volume 0.8"
set sound2 "s_volume 0.7; set sound vstr sound3; Echo Current Status: ^1volume 0.7"
set sound3 "s_volume 0.6; set sound vstr sound4; Echo Current Status: ^1volume 0.6"
set sound4 "s_volume 0.5; set sound vstr sound5; Echo Current Status: ^1volume 0.5"
set sound5 "s_volume 0.4; set sound vstr sound6; Echo Current Status: ^1volume 0.4"
set sound6 "s_volume 0.3; set sound vstr sound7; Echo Current Status: ^1volume 0.3"
set sound7 "s_volume 0.2; set sound vstr sound8; Echo Current Status: ^1volume 0.2"
set sound8 "s_volume 0.1; set sound vstr sound9; Echo Current Status: ^1volume 0.1"
set sound9 "s_volume 0; set sound vstr sound0; Echo Current Status: ^1volume 0"
set fov "vstr fov0"
set fov0 "cg_fov 90; set fov vstr fov1; Echo Current Status: ^1fov 90"
set fov1 "cg_fov 95; set fov vstr fov2; Echo Current Status: ^1fov 95"
set fov2 "cg_fov 100; set fov vstr fov3; Echo Current Status: ^1fov 100"
set fov3 "cg_fov 105; set fov vstr fov4; Echo Current Status: ^1fov 105"
set fov4 "cg_fov 110; set fov vstr fov5; Echo Current Status: ^1fov 110"
set fov5 "cg_fov 115; set fov vstr fov6; Echo Current Status: ^1fov 115"
set fov6 "cg_fov 120; set fov vstr fov7; Echo Current Status: ^1fov 120"
set fov7 "cg_fov 125; set fov vstr fov8; Echo Current Status: ^1fov 125"
set fov8 "cg_fov 130; set fov vstr fov0; Echo Current Status: ^1fov 130"
set  speedjump "+sprint; wait 12; +moveup; wait; -sprint; wait; -moveup"
seta lenovo "vstr lenovo1"
seta lenovo1 "weapon 1;wait;wait;wait;wait;wait;+attack2;set lenovo vstr lenovo2"
seta lenovo2 "weapon 1;-attack2;set lenovo vstr lenovo1"
set pbg "vstr pbgon" 
set pbgon "toggleconsole;wait 50;clear;cl_guid;screenshotjpeg;players;wait 50;wait 50;toggleconsole;set pbg vstr pbgoff" 
set pbgoff "toggleconsole;wait 50;condump info.txt; wait 25;toggleconsole;set pbg vstr pbgon;echo ^0ScreenShot ^7GUID ^1Players ^0Condump ^1Saved"
seta walk_on "-speed; set walk_t vstr walk_off"
seta walk_off "+speed; set walk_t vstr walk_on"
seta walk_t "vstr walk_on"
set clock0 "cg_drawclock 0;set clock vstr clock1"
set clock1 "cg_drawclock 1; set clock vstr clock2"
set clock2 "cg_drawclock 2; set clock vstr clock0"
set clock "vstr clock0"
set FFE "+zoom; +attack; -attack; -zoom" 
set mapout "+mapexpand; echo ^6Map ^7is now ^2expanded; set map vstr mapin"
set mapin "-mapexpand; echo ^6Map ^7 is now ^1OFF; set map vstr mapout"
set map "vstr mapout"
set crosshr "vstr crosshaircolor0"
set crosshaircolor0 "cg_crosshairColor black; cg_crosshairColorAlt black; set crosshr vstr crosshaircolor1; Echo Current Status: ^1Crosshair Color ^0Black"
set crosshaircolor1 "cg_crosshairColor red; cg_crosshairColorAlt red; set crosshr vstr crosshaircolor2; Echo Current Status: ^1Crosshair Color ^1Red"
set crosshaircolor2 "cg_crosshairColor green; cg_crosshairColorAlt green; set crosshr vstr crosshaircolor3; Echo Current Status: ^1Crosshair Color ^2Green"
set crosshaircolor3 "cg_crosshairColor yellow; cg_crosshairColorAlt yellow; set crosshr vstr crosshaircolor4; Echo Current Status: ^1Crosshair Color ^3Yellow"
set crosshaircolor4 "cg_crosshairColor blue; cg_crosshairColorAlt blue; set crosshr vstr crosshaircolor5; Echo Current Status: ^1Crosshair Color ^4Blue"
set crosshaircolor5 "cg_crosshairColor cyan; cg_crosshairColorAlt cyan; set crosshr vstr crosshaircolor6; Echo Current Status: ^1Crosshair Color ^5Cyan"
set crosshaircolor6 "cg_crosshairColor magenta; cg_crosshairColorAlt magenta; set crosshr vstr crosshaircolor7; Echo Current Status: ^1Crosshair Color ^6Magenta"
set crosshaircolor7 "cg_crosshairColor white; cg_crosshairColorAlt white; set crosshr vstr crosshaircolor8; Echo Current Status: ^1Crosshair Color ^7White"
set crosshaircolor8 "cg_crosshairColor orange; cg_crosshairColorAlt orange; set crosshr vstr crosshaircolor0; Echo Current Status: ^1Crosshair Color ^8Orange"
set crosshair "vstr crosshair0"
set crosshair0 "cg_drawcrosshair 5; set crosshair vstr crosshair1"
set crosshair1 "cg_drawcrosshair 17; set crosshair vstr crosshair2"
set crosshair2 "cg_drawcrosshair 20; set crosshair vstr crosshair3"
set crosshair3 "cg_drawcrosshair 19; set crosshair vstr crosshair4"
set crosshair4 "cg_drawcrosshair 18; set crosshair vstr crosshair5"
set crosshair5 "cg_drawcrosshair 14; set crosshair vstr crosshair6"
set crosshair6 "cg_drawcrosshair 7; set crosshair vstr crosshair7"
set crosshair7 "cg_drawcrosshair 8; set crosshair vstr crosshair8"
set crosshair8 "cg_drawcrosshair 9; set crosshair vstr crosshair0"
set crosshairsize "vstr crosshairsize0"
set crosshairsize0 "cg_crosshairsize 80; set crosshairsize vstr crosshairsize1; Echo Current Status: ^1CrosshairSize 80"
set crosshairsize1 "cg_crosshairsize 75; set crosshairsize vstr crosshairsize2; Echo Current Status: ^1CrosshairSize 75"
set crosshairsize2 "cg_crosshairsize 70; set crosshairsize vstr crosshairsize3; Echo Current Status: ^1CrosshairSize 70"
set crosshairsize3 "cg_crosshairsize 65; set crosshairsize vstr crosshairsize4; Echo Current Status: ^1CrosshairSize 65"
set crosshairsize4 "cg_crosshairsize 60; set crosshairsize vstr crosshairsize5; Echo Current Status: ^1CrosshairSize 60"
set crosshairsize5 "cg_crosshairsize 50; set crosshairsize vstr crosshairsize6; Echo Current Status: ^1CrosshairSize 50"
set crosshairsize6 "cg_crosshairsize 40; set crosshairsize vstr crosshairsize7; Echo Current Status: ^1CrosshairSize 40"
set crosshairsize7 "cg_crosshairsize 30; set crosshairsize vstr crosshairsize8; Echo Current Status: ^1CrosshairSize 30"
set crosshairsize8 "cg_crosshairsize 20; set crosshairsize vstr crosshairsize0; Echo Current Status: ^1CrosshairSize 20"
set fps00 "vstr fps0"
set fps0 "com_maxFPS 125; set fps00 vstr fps1; Echo Current Status: ^1FPS 125"
set fps1 "com_maxFPS 76; set fps00 vstr fps2; Echo Current Status: ^1FPS 76"
set fps2 "com_maxFPS 43; set fps00 vstr fps0; Echo Current Status: ^1FPS 43"
set time00 "vstr time0"
set time0 "seta cl_timenudge 0; set time00 vstr time1; Echo Current Status: ^1timenudge 0"
set time1 "seta cl_timenudge -10; set time00 vstr time2; Echo Current Status: ^1timenudge -10"
set time2 "seta cl_timenudge -20; set time00 vstr time3; Echo Current Status: ^1timenudge -20"
set time3 "seta cl_timenudge -30; set time00 vstr time4; Echo Current Status: ^1timenudge -30"
set time4 "seta cl_timenudge -40; set time00 vstr time5; Echo Current Status: ^1timenudge -40"
set time5 "seta cl_timenudge -50; set time00 vstr time0; Echo Current Status: ^1timenudge -50"
set packets00 "vstr packets0"
set packets0 "seta cl_maxpackets 76; set packets00 vstr packets1; Echo Current Status: ^1maxpackets 76"
set packets1 "seta cl_maxpackets 60; set packets00 vstr packets2; Echo Current Status: ^1maxpackets 60"
set packets2 "seta cl_maxpackets 30; set packets00 vstr packets3; Echo Current Status: ^1maxpackets 30"
set packets3 "seta cl_maxpackets 100; set packets00 vstr packets0; Echo Current Status: ^1maxpackets 100"
set rate00 "vstr rate0"
set rate0 "rate 25000; set rate00 vstr rate1; Echo Current Status: ^1rate 25000"
set rate1 "rate 34000; set rate00 vstr rate2; Echo Current Status: ^1rate 34000"
set rate2 "rate 35000; set rate00 vstr rate3; Echo Current Status: ^1rate 35000"
set rate3 "rate 36000; set rate00 vstr rate4; Echo Current Status: ^1rate 36000"
set rate4 "rate 37000; set rate00 vstr rate5; Echo Current Status: ^1rate 37000"
set rate5 "rate 38000; set rate00 vstr rate6; Echo Current Status: ^1rate 38000"
set rate6 "rate 39000; set rate00 vstr rate7; Echo Current Status: ^1rate 39000"
set rate7 "rate 40000; set rate00 vstr rate8; Echo Current Status: ^1rate 40000"
set rate8 "rate 45000; set rate00 vstr rate9; Echo Current Status: ^1rate 45000"
set rate9 "rate 50000; set rate00 vstr rate10; Echo Current Status: ^1rate 50000"
set rate10 "rate 55000; set rate00 vstr rate11; Echo Current Status: ^1rate 55000"
set rate11 "rate 60000; set rate00 vstr rate12; Echo Current Status: ^1rate 60000"
set rate12 "rate 65000; set rate00 vstr rate13; Echo Current Status: ^1rate 65000"
set rate13 "rate 70000; set rate00 vstr rate14; Echo Current Status: ^1rate 70000"
set rate14 "rate 75000; set rate00 vstr rate15; Echo Current Status: ^1rate 75000"
set rate15 "rate 80000; set rate00 vstr rate16; Echo Current Status: ^1rate 80000"
set rate16 "rate 85000; set rate00 vstr rate17; Echo Current Status: ^1rate 85000"
set rate17 "rate 90000; set rate00 vstr rate0; Echo Current Status: ^1rate 90000"
set demoon "autorecord; set nextdemo vstr demooff; echo ^2Recording ^7demo"
set demooff "stoprecord; set nextdemo vstr demoon; echo ^7Recording ^1stopped"
set nextdemo "vstr demoon"
set wavon "wav_record; set nextwav vstr wavoff; echo ^2Recording ^7sound"
set wavoff "wav_stoprecord; set nextwav vstr wavon; echo ^7Sound Recording ^1stopped"
set nextwav "vstr wavon"
set info "vstr info_on"
set info_on "cg_drawFPS 1; cg_lagometer 1; b_drawspeed 2,4; b_watermarkalpha 1; set info vstr info_off; echo ^6Info ^7is now ^2ON"
set info_off "cg_drawFPS 0; cg_lagometer 0; b_drawspeed 0; b_watermarkalpha 0; set info vstr info_on; echo ^6Info ^7is now ^1OFF"

set shooton "+attack; cg_crosshairY 1"       
set shootoff "-attack; cg_crosshairY 0"      






unbind F5;
unbind F6;
unbind KP_HOME        
unbind KP_UPARROW    
unbind KP_PGUP    
unbind INS;
unbind HOME;
unbind DEL;
unbind PGUP;
unbind PGDN;
unbind END;

echo "^9:::^0ET CLASS SCRIPT LOADED^9:::";

set axis_team "exec axis.cfg";
set allies_team "exec allies.cfg";

bind KP_RIGHTARROW "set reset vstr axis_team; vstr axis_team"
bind KP_LEFTARROW "set reset vstr allies_team; vstr allies_team"




/// !!!!! Allies
echo "^9/^0/^9/^3>^0Allies Class Script Loaded^3<^9\^0\^9\";
echo "^nCLASS COMMAND KEYS^0: KP_HOME:^NSoldier^1::^0KP_UPARROW:^NEngineer^1::^0KP_PGUP:^nCovertOp^1::^0DEL:^nField OP^1::";
echo "^0END:^nMedic^1::^0PGDN:^nPanzer^1::^0F6:^nResets Classes^1::";

bind F5 "exec start.cfg"; // Starts over from team select
bind F6 "vstr startup"; // Resets allies class menu

set startup "bind KP_HOME vstr soldier_start; bind END vstr medic; bind KP_UPARROW vstr engineer_start; bind DEL vstr fieldop; bind KP_PGUP vstr covertop_start;
vstr startup;

set soldier_start "bind INS vstr soldier_mortar;bind HOME vstr soldier_mg42; bind PGDN vstr soldier_panzer; bind PGUP vstr soldier_flamer; echo ^0Soldier Classes Activated ^cBinds^0: INS:^NMortar^1::^0HOME:^NMG42^1::^0PGDN:^NPanzer^1::^0PGUP:^NFlamer^1::";
set soldier_mortar "team b 0 35; say_team ^nGoing^9:^0Soldier^9/^0Mortar^3<^9\^0\^9\; echo ^nGoing^9:^0Soldier^9/^0Mortar^3<^9\^0\^9\";
set soldier_mg42 "team b 0 31; say_team ^nGoing^9:^0Soldier^9/^0MG42^3<^9\^0\^9\; echo ^nGoing^9:^0Soldier^9/^0MG42^3<^9\^0\^9\";
set soldier_panzer "team b 0 5; say_team ^nGoing^9:^0Soldier^9/^0Panzer^3<^9\^0\^9\; echo ^nGoing^9:^0Soldier^9/^0Panzer^3<^9\^0\^9\";
set soldier_flamer "team b 0 6; say_team ^nGoing^9:^0Soldier^9/^0Flamer^3<^9\^0\^9\; echo ^nGoing^9:^0Soldier^9/^0Flamer^3<^9\^0\^9\";

set medic "team b 1 8; say_team ^nGoing^9:^0Medic^3<^9\^0\^9\; echo ^nGoing^9:^0Medic^3<^9\^0\^9\";

set engineer_start "bind INS vstr engineer_thompson; bind HOME vstr engineer_garand; echo ^0Engineer Classes Activated ^cBinds^0: INS:^NThomson^1::^0HOME:^NGarand::";
set engineer_garand "team b 2 24; say_team ^nGoing^9:^0Engineer^9/^0Garand^3<^9\^0\^9\; echo ^nGoing^9:^0Engineer^9/^0Garand^3<^9\^0\^9\";
set engineer_thompson "team b 2 8; say_team ^nGoing^9:^0Engineer^9/^0Thompson^3<^9\^0\^9\; echo ^nGoing^9:^0Engineer^9/^0Thompson^3<^9\^0\^9\";

set fieldop "team b 3 8; say_team ^nGoing^9:^0Field Op^3<^9\^0\^9\; echo ^nGoing^9:^0Field Op^3<^9\^0\^9\";

set covertop_start "bind INS vstr covertop_garand; bind HOME vstr covertop_fg42; bind PGUP vstr covertop_sten;echo ^0Cover Op Classes Activated ^cBinds^0: INS:^NGarand^1::^0HOME:^NFG42^1::^0PGUP:^NSten^1::";
set covertop_garand "team b 4 25; say_team ^nGoing^9:^0Covert Op^9/^0Garand^3<^9\^0\^9\; echo ^nGoing^9:^0Covert Op^9/^0Garand^3<^9\^0\^9\";
set covertop_fg42 "team b 4 33; say_team ^nGoing^9:^0Covert Op^9/^0FG42^3<^9\^0\^9\; echo ^nGoing^9:^0Covert Op^9/^0FG42^3<^9\^0\^9\";
set covertop_sten "team b 4 10; say_team ^nGoing^9:^0Covert Op^9/^0Sten^3<^9\^0\^9\; echo ^nGoing^9:^0Covert Op^9/^0Sten^3<^9\^0\^9\";





/// !!!!! Axis
echo "^9/^0/^9/^3>^1Axis Class Script Loaded^3<^9\^0\^9\";
echo "^nCLASS COMMAND KEYS^7: KP_HOME:^NSoldat^1::^7KP_UPARROW:^NEngineer^1::^7KP_PGUP:^nCovertOp^1::^7DEL:^nField OP^1::";
echo "^7END:^nMedic^1::^7PGDN:^nPanzer^1::^7F6:^nResets Classes^1::";
bind F5 "exec start.cfg"; // Starts over from team select
bind F6 "vstr startup"; // Resets axis class menu

set startup "bind KP_HOME vstr soldier_start; bind END vstr medic; bind KP_UPARROW vstr engineer_start; bind DEL vstr fieldop; bind KP_PGUP vstr covertop_start;
vstr startup;

set soldier_start "bind INS vstr soldier_mortar;bind HOME vstr soldier_mg42; bind PGDN vstr soldier_panzer; bind PGUP vstr soldier_flamer; echo ^7Soldat Classes Activated ^cBinds^7: INS:^NMortar^1::^7HOME:^NMG42^1::^7PGDN:^NPanzer^1::^7PGUP:^NFlamer^1::";
set soldier_mortar "team r 0 35; say_team ^nGoing^9:^7Soldat^9/^7Mortar^3<^9\^0\^9\; echo ^nGoing^9:^7Soldat^9/^7Mortar^3<^9\^0\^9\";
set soldier_mg42 "team r 0 31; say_team ^nGoing^9:^7Soldat^9/^7MG42^3<^9\^0\^9\; echo ^nGoing^9:^7Soldat^9/^7MG42^3<^9\^0\^9\";
set soldier_panzer "team r 0 5; say_team ^nGoing^9:^7Soldat^9/^7Panzer^3<^9\^0\^9\; echo ^nGoing^9:^7Soldat^9/^7Panzer^3<^9\^0\^9\";
set soldier_flamer "team r 0 6; say_team ^nGoing^9:^7Soldat^9/^7Flamer^3<^9\^0\^9\; echo ^nGoing^9:^7Soldat^9/^7Flamer^3<^9\^0\^9\";

set medic "team r 1 3; say_team ^nGoing^9:^7Medic^3<^9\^0\^9\; echo ^nGoing^9:^7Medic^3<^9\^0\^9\";

set engineer_start "bind INS vstr engineer_mp40; bind HOME vstr engineer_k43; echo ^0Engineer Classes Activated ^cBinds^0: INS:^NMP40^1::^0HOME:^NK43^1::";
set engineer_k43 "team r 2 23; say_team ^nGoing^9:^7Engineer^9/^7K43^3<^9\^0\^9\; echo ^nGoing^9:^7Engineer^9/^7K43^3<^9\^0\^9\";
set engineer_mp40 "team r 2 3; say_team ^nGoing^9:^7Engineer^9/^7Mp40^3<^9\^0\^9\; echo ^nGoing^9:^7Engineer^9/^7Mp40^3<^9\^0\^9\";

set fieldop "team r 3 3; say_team ^nGoing^9:^7Field Op^3<^9\^7\^9\; echo ^nGoing^9:^7Field Op^3<^9\^0\^9\";

set covertop_start "bind INS vstr covertop_k43; bind HOME vstr covertop_fg42; bind PGUP vstr covertop_sten; echo ^7Cover Op Classes Activated ^cBinds^7: INS:^NK43^1::^7HOME:^7FG42^1::^7PGUP:^7Sten^1::";
set covertop_k43 "team r 4 32; say_team ^nGoing^9:^7Covert Op^9/^7K43^3<^9\^0\^9\; echo ^nGoing^9:^7Covert Op^9/^7K43^3<^9\^0\^9\";
set covertop_fg42 "team r 4 33; say_team ^nGoing^9:^7Covert Op^9/^7FG42^3<^9\^0\^9\; echo ^nGoing^9:^7Covert Op^9/^7FG42^3<^9\^0\^9\";
set covertop_sten "team r 4 10; say_team ^nGoing^9:^7Covert Op^9/^7Sten^3<^9\^0\^9\; echo ^nGoing^9:^7Covert Op^9/^7Sten^3<^9\^0\^9\";





bind ENTER "vstr map"
bind , "players;; wait 50;toggleconsole"
bind . "vstr info"
bind 0 "setspawnpt 5;say_team ^1Spawn 5 ;play sound/menu/select.wav"
bind 1 "weaponbank 4;wait 120;+attack;wait 20;-attack;wait 10;kill; forcetapout"
bind h "playdead"
bind 5 "setspawnpt 0;say_team ^1Spawn 0 ;play sound/menu/select.wav"
bind 6 "setspawnpt 1;say_team ^1Spawn 1 ;play sound/menu/select.wav"
bind 7 "setspawnpt 2;say_team ^1Spawn 2 ;play sound/menu/select.wav"
bind 8 "setspawnpt 3;say_team ^1Spawn 3 ;play sound/menu/select.wav"
bind 9 "setspawnpt 4;say_team ^1Spawn 4 ;play sound/menu/select.wav"
bind [ "mapzoomout"
bind ] "mapzoomin"
bind x "vstr walk_t"
bind k "vstr crosshr"
bind l "vstr clock"
bind m "vstr st"
bind n "vstr FFE"
bind p "s_volume 0; Echo ^1Sound Mute"
bind BACKSPACE "vstr AxisAllies"
bind PAUSE "vstr pausetoggle"
bind UPARROW "vstr gamma"
bind DOWNARROW "vstr sens"
bind LEFTARROW "vstr fov"
bind RIGHTARROW "vstr sound"
bind v "vstr speedjump"
bind F9 "vstr crosshair"
bind F10 "vstr crosshairsize"
bind F11 "vstr nextwav"
bind F12 "vstr nextdemo"
bind KP_LEFTARROW "set reset vstr allies_team; vstr allies_team"
bind KP_RIGHTARROW "set reset vstr axis_team; vstr axis_team"
bind KP_END "vstr fps00"
bind KP_DOWNARROW "vstr rate00"
bind KP_PGDN "vstr packets00"
bind KP_INS "vstr nextstatus"
bind KP_DEL "vstr time00"
bind MOUSE1 "+vstr shooton shootoff"
bind MOUSE3 "vstr lenovo"



By Lenovo Cfg Experience

now San Tino 2

Edited by JirenTV
  • Like 1

Share this post

Link to post
Share on other sites

or /bind k kill.

Share this post

Link to post
Share on other sites

or / ignore player i

  • Like 1

Share this post

Link to post
Share on other sites

Having a bind for kill is likely more important than having a bind for prone, which comes default. Having a bind for the timer is also important, but it's not vital. The main use for the rest of the config is to make sure you have consistent FPS (43, 76, 125 are preferred due to game bugs) and high enough contrast to easily spot the enemy. That's it.


The reason the kill bind is so important is that it regroups you with your team, renews HP, and renews ammo. It also changes your position on the map, which may or may not be a good trade. This judgement requires more experience, but a sketch of the decision procedure is something like:

- Do I have any ammo to dole out damage?

- When do I expect to die during the next push? E.g. will my team get here in time to back me up. If you're in a surprising position, how likely are you to deliver enough flank damage to allow your team's push through.

- Is a spawn point being contested? Killing out teleports you to that spawn point and even gives you a shield to help defend it.


You must pay attention to the spawn timers for any of this to work out. "Full spawn" refers to going into limbo just after the respawn, and it hurts. Make sure this doesn't happen to you, make sure this happens to your enemy. Hardcore is more forgiving with its 14/18 second spawn intervals. In competitive it's more often 20/30 seconds, giving it an even stronger effect.


This is a very important bind to help your macro play. It's a shame that it doesn't come as a standard bind.

  • Like 3
  • Thanks 1

Share this post

Link to post
Share on other sites

Game awareness is more than using headphones. In fact, I play with music in the background, making it less likely for me to hear your footsteps. Headphones are much more important when there are fewer total players. Hearing footsteps in a 1v1 is vital, hearing footsteps in a 10v10 is not as important. The more important point is map control.

Whether you're trying to do the objective or just playing for frags, you want to maintain map control. The longer you can stay alive the more time you have to deliver damage. Even if you cannot get the frag, it's important to deliver damage so the enemy cannot run over the rest of your team so easily. It's very important that you not get aced by a surprise attack. The way you prevent surprise is "knowing" where the enemy is at.

You can have a reasonable stochastic model of enemy positions as a function of the spawn times and average enemy travel speed. Sometimes these probabilities are certainties. If you know the enemy spawn time and you've been reading the obituaries and there's only one spawn point for the enemy, then there is a moment where you know their exact position. As time goes forward their position becomes less certain, assuming you are not directly observing them. You also know the limit of their maximum distance from the spawn, their wavefront, since you know their travel speed. For example, "Lotto" (lottery) refers to putting splash damage (can also refer to pre-firing) on the map, hoping to hit something. They don't know for certain that you will be there, only that it's probable. The "pro wait" guards against this: avoid being at the wavefront (maximum travel from spawn) as that is more likely to catch lotto damage.

Every map is different, but in general ET maps are more closed or indoors (they're not like baserace), giving rise to particular "routes" or "vias" which are pathways from the spawn. If you're defending, you want to cover as many routes as possible without "leaking" enemies, which is letting them travel past you unchecked on their way to the objective. If you think of the map as a graph, the edges are the corridors and the nodes are the openings where more than one edge meets. Some nodes dominate the path from the attacker's spawn to the attacker's objective, meaning every pathway goes through the node. As the defense you want to position on these nodes, guaranteeing you don't leak enemies. However, most maps are designed to avoid having dominator nodes like this to give the attack other options. I'm going to make up the word "dominance degree" to describe this characteristic of a node: the probability that an enemy travels through this node. You want to hold nodes with a high degree of dominance, but it's worthless to hold it if enemies leak through other paths that can flank this node. This requires communication and coordination on defense. For example, if after the enemy respawn none of them come through your node, it's very likely that they took another path (although it's possible they are waiting). At this point you should either rotate to the other node to help that side of the defense or you can gain more of the map by pushing up to hold a high dominance node even closer to their spawn. Keep in mind that such a tight hold on the spawn only pays out if your other defense does not fail -- because if they do, you will have a slow response to the objective as you must cross the map (use a killout to mitigate this). When you have a tight hold on their spawn it very often coerces the enemy to take alternative routes. After stopping their push on your route, look to push into their other likely routes for a flank and then reset (killout). Look around at what fraction of your team is on your route to make a reasonable guess as to whether the other node is sufficiently guarded. Keep in mind that if the attack is coordinated they can create a numbers advantage for themselves when your team is split like this.

As defense you're largely just fighting for these nodes (yes, you're basically camping). When you control these nodes, the enemy cannot get behind you, forcing the attack to muscle through choke points. If they do get behind you, you have to retreat or "dig" them out. Ignoring them just invites a flank. If you're attacking, this is a valuable thing to do for your team to make the defense split their attention (or just take the flank kills if they ignore you). Doling out unchecked damage is always a plus for your team.

To recap why map control is important:
- You don't want to take unchecked damage (you do want to deliver unchecked damage)
- You want to land the first hit in a duel. The more likely you are to have your crosshair on the enemy when rounding a corner the more likely you'll win the fight.
- You don't want to be outnumbered. Assuming a relatively small skill gap, you're going to lose a 2v1 gun fight. You can be happy about going 1:1, so long as there's no enemy medic to mitigate your kill.
- You want to force your enemy through choke points. This is basically the same as the previous point about being outnumbered. Choke points force your enemy into a 1v1 (ideally many to one if your team is helping) despite they're in a pack. Sometimes they even deliver team damage trying to get at you, thwarting their own push. Don't be this person. Likewise, don't let your teammates fight solo against multiple enemies. The side with the higher damage throughput is likely to win -- increase your team's throughput by increasing its damage bandwidth.

  • Like 3
  • Thanks 1

Share this post

Link to post
Share on other sites

Everybody knows that the higher the Kill/Death ratio (K/D) the better the player. Right?


Not exactly. A better measurement for killing power is overall damage and accuracy. Even this measure has problems, as there are a lot of pathological cases that can inflate stats. So let's remember the fundamentals to ground ourselves, as it often seems like a pub is just chaos.


An objective is to be guarded or attacked. By default the offense loses, meaning it is the offense's responsibility to make a move whereas the defense can hang back and camp. If there were no weapons the game would be reduced to a race and some shit show of never-ending planting/defusing and likely a lot of pushing. With weapons you can now remove the enemy from the map to make way for the objective. Already from this we know that killing AFK's in spawn are not worth as much as killing enemies on the objective. The same applies to wasting resources attacking/defending anything that's not related to the objective.


Players can be removed from the map, but they come back at regular intervals. This creates "waves" of enemies, where the wave is strongest at the respawn time and gradually weakens as the players flow out of the spawn. Kills on enemies just after their respawn are worth more than on enemies who are about to respawn. A kill on an enemy about to respawn is not worthless, as it still forces them back to a respawn point and removes their map pressure. If you know their respawn time you can purposely wait until after their respawn to kill them for maximum effect. Skilled players will "push out" when their respawn is approaching to deal damage to the next enemy wave before resetting. Remember, the kills themselves are only valuable insofar as they help you achieve the objective. If you don't gain an objective or map control, the kill is worthless.


You don't necessarily have to kill an enemy. If they run away then your job is essentially done and you can shift your focus to better targets. Don't mindlessly chase people. Likewise you can always provide damage assistance even if you don't expect to get the kill. The extra damage makes the enemy less likely to land hits on your teammate, and also you have a more clear shot since you're likely not taking damage while shooting.


Just as a kill on an enemy about to respawn is not worth much, a kill on an enemy who gets full revived is worth even less because they get to keep their map pressure. When a player is revived they get a shield, providing a barrier for the medic. Sometimes players will burn all of their ammo trying to get at the medic. Don't fall for this. There is a similar trick to proning inside gibs. With experience you can know the extents of the hitboxes. Until then, you're likely being tricked into a reload death.


Not all players are equal. A kill on a low skill player is not worth the same as a kill on a high skill player. Unfortunately this leads to successful strategies like letting the low skill players charge in first and allow the high skill players to clean up. Unfortunately for the same reason it's not always to your advantage to spend resources on low skill players. It's especially frustrating when they bleed you when you don't comply. Weapon switch leaves a player vulnerable for a time, so a high skill might decide you are not worth the risk. Here are some tips:

  • Die in a better spot. Don't lure your medic into a meat grinder.
    • Die inside choke points that block enemy movements, like doorways. Be sure to crouch while fighting so that your medic can get in some shots.
    • Crouch aiming might be too difficult for you. That's ok, you can still be useful, especially if you're a laggy son-of-a-b***. Do your death charge while maintaining presence of mind: wait until you have backup, don't block your backup's line of sight, move around so that the enemy have to use more resources to kill you, and try to take down medics.
  • When requesting ammo or meds, don't stare at the person. You'll likely notice that they are focused on a choke point. You should instead also focus on that choke point while requesting resources so that at least someone is watching. When you shoot or get shot at it gives your teammates information about the map.
  • This might be asking a lot, but don't bleed your high skill teammates. Instead, treat them as your cash cow. Feed them ammo and meds, revive them ASAP, and help shoot along side them without getting in their way. It's important to both help contribute damage and take some of the pressure off them by luring enemy attention. The best part is that when you die you'll notice that a high skill player has you revived in no time.

So now you know the complications with reducing player quality down to a number. It's situational. If you think it's kills per death, would you say someone with 5:1 did better than 50:40? If it's damage, is someone who abuses artillery or panzer really that skilled? If it's accuracy is someone with 100% accuracy but only 30 shots skilled? How do revives factor into your model? None of these stats, as tracked by ET, are weighted by the enemy's quality. So don't worry about racking up deaths as long as you're getting work done on the objective.


  • Like 4
  • Thanks 1

Share this post

Link to post
Share on other sites
22 hours ago, efool said:
  • Die in a better spot. Don't lure your medic into a meat grinder.
    • Die inside choke points that block enemy movements, like doorways. Be sure to crouch while fighting so that your medic can get in some shots. 
    • Crouch aiming might be too difficult for you. That's ok, you can still be useful, especially if you're a laggy son-of-a-b***. Do your death charge while maintaining presence of mind: wait until you have backup, don't block your backup's line of sight, move around so that the enemy have to use more resources to kill you, and try to take down medics.
  • This might be asking a lot, but don't bleed your high skill teammates. Instead, treat them as your cash cow. Feed them ammo and meds, revive them ASAP, and help shoot along side them without getting in their way. It's important to both help contribute damage and take some of the pressure off them by luring enemy attention. The best part is that when you die you'll notice that a high skill player has you revived in no time.


 Good stuff! Dying right as an engie is important. For example, at supply if you can die right at the gate rather than in the bottom of the building or inside the depot gate right before, please do so. Don't make the medic and yourself get crossfired from every direction. 


Being aware of the teammates behind you is huge too. If you can avoid strafe dancing infront of people please do so, move wide and let others help you rather than get bled by your teammates and the enemy. Spreading also creates a wide cone making it more difficult for a single enemy to killing multiple players.

  • Like 1

Share this post

Link to post
Share on other sites
Posted (edited)

"What's your sensitivity?" you ask, after switching to spectator in an attempt to comprehend what just happened to you.


"It's 1.0," I reply. Truely. And then I let you know where you can get my config. (2000 dpi if you're curious)


But that won't help you. You aren't asking the right question. It becomes clear when I sit down at your computer and do roughly the same thing to people. So what the hell is going on.


When I sit down I'm going to make a few tweaks:

  • I get 76 or 125 stable FPS
  • I max out maxpackets and rate (this gets technical and might be worth another post)
  • I get as much player constrast as I can (this is subjective)
  • I put on my preferred crosshair (cyan dot) (also subjective)
  • I turn off mouse acceleration (subjective -- but is there anyone who actually prefers mouse accel?)
  • I adjust the sensitivity until I can mostly track a non-sprinting target (practice on teammates running by)
    • I also like mAus's advice on being able to comfortably do a 180 degree turn

And that's it. There's no secret sensitivity, no special script. I need to be able to see my environment, my enemies, and my crosshair. Then I make it so that the crosshair overlaps the enemies. Simple, minus the 10 years of building up muscle memory to instinctively move the mouse.


If you were in awe of a friend who could play piano, you wouldn't think it's the brand of piano that gives them that sound. While that does matter, you would recognize it's mostly to do with their ability to push the keys at the right times. It's a nuanced skill they've developed, likely through years of practice. When they tune it they need feedback to know how to adjust the strings.


In order to frag I need to easily see the opponent and then put the cursor on them quickly (initial snap) and then smoothly track them until getting the kill. You're going to need "good enough" hardware to do this, which most people have by now. Get a laser mouse, a good (big) mousepad, a low-latency monitor, and that's about it. This may sound strange, but part of the hardware is making sure your body is able to interact with the game fluidly. You need to be able to see the screen, hear the sounds, move the mouse, and punch the keys both comfortably and accurately.


You do not share my hardware configuration. I have long arms and fingers. I grip the mouse like a claw and move my entire arm for coarse aiming and use a combination of wrist and fingers for fine aiming (wrist movements for snapping and fingers for finer tracking). Also, my mouse happens to be outside my peripheral vision and is at a different elevation from my keyboard. The point is not to imitate this set up but rather to recognize that you need to dial your configuration into something comfortable for you. If you don't or can't interact with your hardware like this then my sensitivity setting is of no use to you.


What you're really asking is how you can achieve the same effect. If you're serious about trying to do what I do (or anyone else) you would record and watch my games. Then record yourself playing and try to compare the two. Actually, you may not even need to see me playing: just record yourself and watch it as a critic. You'll likely be able to figure out on your own what you're doing wrong, then you can focus on correcting that.


You need to have control of your body and mind (emotions). It's unacceptable to miss non-moving targets or flanks (and they had better be head-shots!). Figure out what's going wrong, because that's the equivalent of missing a layup in the ET world. Sometimes when I spectate a player I'm reminded of the head bobs of a toddler who hasn't developed motor control. Train, record, and be honest with yourself about your ability to put the crosshair on specific targets. Focus on doing it accurately first, then try to develop speed. Over-correcting squirrel aim isn't going to beat out slow methodical tortoise aim. Load up a local server in developer mode with hit boxes rendered to make sure you understand them, since hit boxes don't necessarily match the player models.


I think you'll find that your damage numbers will go up just by practicing your stationary crouch aim, coupled with occupying strategic map locations. In a pub where there's chaos, a lot of opportunities open up to the point that it's just a question of whether you have the capability to capitalize on it. Your team fight will improve because you can casually pick off enemies from afar. You can deliver damage while not blocking your team. You can "peek" enemies around obstacles, where you line up the vision to see only 1 or 2 enemies in a pack of 3 or 4. You can gib critical players from afar. You will exhibit better control in general and have a larger impact on the game. But you can't do any of this if you can't aim. Speed matters, as you'll find opportunities leave just as fast as they arrive.


"Are you saying I don't need to strafe to dodge bullets?"
I'm saying that when you're ready, you won't need to.


Strafing is still important in aiming. It gives you a nice linear trace path with the cursor, assuming your target is traveling over level terrain. It's also effective to try to match your enemy's strafe pattern in a duel. But if your first instinct is to strafe wild to avoid shots that are not even coming at you then something is wrong. You likely learned this against lower skill enemies who can't hit the backside of a barn or have no confidence in your own aiming ability. It's a whole different game when your enemy can actually aim. You better put them in limbo first before they do it to you. You want go from flailing your arms to throwing straight punches.


Which is another great point: play against players better than you. But don't play against players that are so much better that it's overwhelming (the point here is to learn from your mistakes). You know that you don't get any better by fragging bots (well, it is useful for figuring out hit boxes and otherwise understanding how a 3-dink is supposed to go) -- so why do you think beating up on people worse than you will make you better? Especially starting out, when you get wrecked you're in a sense learning what doesn't work. Consider that everybody had to start at the bottom and there does seem to be a ceiling on skill level. That means you can catch up.


Edited by efool

Share this post

Link to post
Share on other sites

So you get a double kill, and then another, and then you're down to pistols battling the fourth until you finally die. That's a pretty good run, right?


That depends. If you didn't gib them and that fourth enemy full revives the other three, most of your work has been undone. They lost ammo, sprint, charge, and some time, but now they have strong positioning and a numbers advantage going into the next fight. You can be proud of your individual fragging ability, but really you lost since they're still close to full strength while your team has to wait for you to re-deploy.


It's helpful to look at ET in terms of resources. You start with a fixed amount of hit points (HP), ammunition, sprint, and charge, among other miscellaneous things like artillery/airstrike timeouts, fire rate, class limits, panzer, etc. These resources are renewed at regular intervals either through respawn or just the charge/sprint/HP (medic) bar recharging. Time is a resource. These resources are multiplied by the number of players, except some shared resources like airstrike timeout and class limits.


To better demonstrate the time example, an SMG (MP40 or Thompson) does 18 damage, 50 for a headshot (there's falloff with range), per bullet with a 30 bullet clip size before a reload is needed. A reload takes 2400ms, or 0.65*2400=1560ms with light weapons level 2. A weapon switch only takes 250ms. A pistol carries 8 shots, does 18 damage (50 for headshot), and a has a 1500ms, or 0.65*1500=975ms, reload time (akimbos have a base 1755ms reload time). With 100% accuracy you can deliver 30*50=1500 damage in one clip of an SMG over 150*30+100=4600ms (150ms per bullet, 100ms SMG delay). Add 8*50=400 damage for the pistol over a time of 250*8=2000ms for a total of 1900 damage over 4600+250+2000=6850ms (250ms for weapon switch) until you need a breather to reload. The enemy has 100+10*number_of_medics_on_team hit points (capped at 125), plus 15 more if they have battle sense level 3, plus 12% more hit points if they're a medic:

  • 0 medics:
    • 100
    • 115 (battle sense 3)
  • 1 medic:
    • 110
    • 123 (medic)
    • 125 (battle sense 3)
    • 140 (battle sense 3 and medic)
  • 2 medics:
    • 120
    • 134 (medic)
    • 135 (battle sense 3)
    • 151 (battle sense 3 and medic)
  • 3 medics:
    • 125
    • 140 (battle sense 3 or medic)
    • 156 (battle sense 3 and medic)

Players are forced into limbo at -75 HP and gibbed at -175 (aside: in Quake "gibbed" means the body explodes into pieces, like giblets. It's referring to the amount of overkill. In ET we still call it "gibbing" just by forcing them into limbo so that they cannot be revived, despite their corpse remains). In the best case it takes 4 shots (3 headshots, and one body or head shot) to kill a full HP medic, and at best 1 more to gib (4 head shots to down with 200 damage, and then either 1 more head shot or 2 more body shots to force into limbo). Without gibbing you can take down at most 30/4=7 full HP medics over about 5 seconds. So even if you're fighting against an aimbot there is a limit to its damage output! The worst thing you could do is give it time to reload. If each of those 7 opponents land at least one shot, that's 126 damage. If one of them lands a head shot, that's 158 damage and the aimbot is now dead and cannot affect the game until the next respawn. That's only one shot from each! But if funneled into the aimbot one at a time there is a better chance that fewer shots land since your chances to land a hit go down when taking damage. Another good way to peeve that aimbot is to insta-revive your teammate in front of you, using the revive shield as cover. They'll run out of ammo eventually.


This case is pathological, but the principle remains. Superior teamwork tends to win out. Teamwork doesn't just mean giving out ammo and med packs, it means being in the right places at the right times and having an effect on the map. When you fight with superior numbers, and especially if you can coordinate focus fire, your enemy is removed at a faster rate and thus your team incurs less damage. The game dynamics shift as you add more players.


Be effective and use your resources. Everyone understands that when there are AFK's in spawn or they are otherwise at a player deficit the game is much harder. You would say those AFK's have no effect on the game, so it's as if they're not even playing. But realize also that every time you don't contribute to a team fight you may as well be AFK. Being nearby isn't enough. If you stand behind your star player feeding them ammo and meds but never contribute any damage or take any damage, are you really that effective? If aimbots can get overwhelmed they your lone teammate certainly can as well. Take it upon yourself to not allow that.


Every time your sprint bar, charge bar, and health bar is full (as a medic) you are losing the resources that you would otherwise have from regeneration because you didn't use them! This doesn't mean that you should always have your med packs out, but rather you should be mindful of the trade you're making. If you're tucked behind a corner supporting a teammate who's shooting but there isn't enough room for you to shoot alongside them, you should pay the cost of weapon switch to needle now instead of later where there's risk your medic gets gibbed (you weren't doing anything else anyways!). When there's a lull in the battle, pay the weapon switch cost now to resupply your team and allow them to reload rather than later, because chances are you weren't doing anything anyways. If you're not a medic but your medic teammate is being overwhelmed, jump in front of them to absorb the damage! Your medic can restore HP, you cannot. It's a better trade if you die instead so that the revive resource can be used. Be mindful of your respawn time, since it's basically a delivery of (almost) free resources at fixed intervals. The only time you should be doing nothing is when you're on defense and the entire offense is dead. This almost never happens in pub.


Here is an assortment of things I've noticed people don't capitalize on:

  • Be fast.
    • You're racing against the enemy spawn time.
    • You're racing the enemy to key nodes on the map.
    • You're racing to have as much effect as you can before your respawn.
  • Needle revive, whether with a TK or without, is much faster than individual packs. Save those for yourself.
  • Build up med caches for your team during your down time.
  • Don't hang around the spawn point waiting for a medic to heal you (why the hell didn't you killout to respawn in? You'd better have shit tons of ammo or a disguise to be worth my time)
  • Sprint out of the spawn.
  • Push teammates in front of you to create space for yourself and also get them to their destination faster. You're all flowing in the same direction.
  • Never flow against your team. I always shoot these people as suspected of disguise, but really I would just TK them on principle. We all get shot and we all die. Just try to line that up with your re-spawn rather than slow down the rest of your team.
  • You spawn with a shield. Once you attack you lose the shield.
  • Don't stand in the vias blocking everyone's path. And no, it's not a good idea to set up your mortar right on your team's via.
  • Don't place artillery on your team's vias. It's hard to imagine someone does this on purpose, so maybe the advice should be to learn and remember the important vias to an objective. That also sounds obvious, but nontheless it happens over and over. Realistically it's likely teammates who want enemy damage no matter how much it screws over their own team.
  • Don't bleed your teammates! If they're playing wild and strafing in front of you, change tack and pull out the needle to salvage the situation. If you're a panzer or rnade it's probably better for you to lead the charge rather than blow up your team.
  • Don't prime a grenade in the middle of a fight, especially if you're leading! Grenades are useful for lobbing over your teammates when you cannot directly participate in a fight. The same goes for rifle grenades, but it's perfectly fine to lead with rifle grenades.
  • Shoot your rifle grenades up high over your teammates so that you don't hit them (jump if you have to). Hit the hard to reach places or otherwise common hiding places.
  • Don't shoot a panzer from behind your team's push. Either lead the charge or try to get a different elevation so that you're shooting outside your team's plane of attack.
    • Actually, if you're a panzer, just spawn kill the shit outta the other team. If you can put out even just one medic full then you've done your job.
  • When your teammate is shooting but you cannot join, have the needle ready. After 30 bullets if they aren't taking much damage you're going to swap with them so that they can reload and in turn revive you when you need it while you take over shooting.
  • When you kill an enemy and they have a medic teammate waiting in the wings, wait to gib until the medic attempts to revive. You can optionally try your hand at acing the medic, but it really goes south when you fail. This all depends on how much distance the medic needs to travel from behind their cover.
  • Revive engineers when they die while building an objective. They get to continue building while being revived, guaranteeing the build. You have to kill the medic first or otherwise block the medic's revive to combat this.
  • If you're going to killout then trip any nearby mines before doing so (or just let them kill you).
  • Medics can defuse mines faster than engineers by tripping them from maximum distance and then healing up.
  • If you have a medic nearby, just run over the mines and take a death to save time. The medic will revive.
    • If they're already spotted then it's worthwhile just to grenade them.
  • Dynamite and satchels can explode objectives from surprisingly far.
  • Crouching reduces the amount of weapon spread. Burst firing helps too.
  • Know timings.
    • On hardcore shields last 4 seconds.
    • Grenades take 4 seconds to explode.
    • Artillery takes 5 seconds for the first shell, which is always accurate.
    • Airstrikes take 5-6 seconds, or 6-7 seconds with signals level 3. The path is perpendicular (mostly) to the can's throw trajectory. Airstrikes and artillery have some randomness to their path and timings.
    • The panzer takes a second to fire. (you might want to double check these numbers)
  • Rifle grenades can be shot across the map. You can practice specific shots for specific objectives and spawn vias.
  • When deployed on a steep slope, mortars can be shot horizontally like rifle grenades.
  • It's more effective to snipe with high sensitivity so that you can undo the recoil quickly.
  • If you like to play SMG, you can have two SMG's as a soldier.
  • You can change your SMG to the type your enemy carries to help sustain your ammunition.
  • Look to fill niches in a team. Choose a player class that your team needs but other don't want. By default just play medic.
  • Give teammates space to move and back up -- don't crowd or block them while remaining close enough to revive them. You can read the situation by watching the bullet trails and their health drop to know when they're going to try to retreat or die.
  • Anticipate team deaths to have the fastest possible revive. Especially for teammates who do not move much while shooting, you can start to revive as soon as they're below the threshold but are not yet dead.
  • When alone, peek corners (not the ET lean thing) to limit incoming damage. When you have help, you can try going "broad" on a corner, where you over extend from cover to give your teammate room to shoot with you. Unfortunately some teammates leave you hanging, so try this with caution.
  • Give space for your teammates to shoot with you. There's no reason you have to hog the whole doorway on frostbite next to the command post when the enemy very clearly has to come up a very confined choke point (the ladder). Two can DPS better than one.
  • Your chances to get revived depends a lot on the proximity and safety of your nearby medics. Die in front of them or in front of choke points. Don't die in some corner where your medic has to turn their back to the enemy just to revive you.
  • Cover your teammate's blind spots. If you see them covering one way, you should cover a different way. Likewise you can make assumptions about enemy positions based on your own team's coverage.
    • Unless your team doesn't shoot enemies when they see them. Unfortunately this happens all the time, so use with caution. Don't be that person.
  • When someone is crouched in front of you looking straight up, that's the universal sign for "stack on top of me to jump over this obstacle." Don't just stand there staring like an idiot. Now that I think about it, that's probably not the person you want to send in for special operations.
  • Wait to capture flags until just before the re-spawn -- either yours or theirs.
    • On sp_delivery when someone stacks up to the wall and is waiting outside to capture the flag, get ready to killout so that you spawn at the flag. It sucks when you get a successful capture but have no follow up from your team! Pointless!
  • Goldrush is a real test to see how well the offense can play together. The offense likes to stop short of the objective at the bridge and in the alley rather than try to push into the defense spawn or control the courtyard, presumably because they don't like walking into meat grinders. You have 14 seconds to push into the courtyard and subsequently the bank. And since the defense spawns every 18 seconds, you want to control the courtyard so that you can suppress the defense as they exit their spawns through choke points.
  • Know that when your teammate pushes in and you don't back him up, you've failed despite it isn't necessarily recorded in the stats.


  • Like 1
  • 100 2

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

About Us

We are glad you decided to stop by our website and servers. At Fearless Assassins Gaming Community (=F|A=) we strive to bring you the best gaming experience possible. With helpful admins, custom maps and good server regulars your gaming experience should be grand! We love to have fun by playing online games especially W:ET, Call of Duty Series, Counter Strike: Series, Minecraft, Insurgency, DOI, TF2 & Battlefield Series and if you like to do same then join us! Here, you can make worldwide friends while enjoying the game. Anyone from any race and country speaking any language can join our Discord and gaming servers. We have clan members from US, Canada, Europe, Sri Lanka, India, Japan, Australia, Brazil, UK, Austria, Poland, Finland and many other countries. It doesn't matter how much good you are in the game or how much good English you speak. We believe in making new friends from all over the world. If you want to have fun and want to make new friends join up our gaming servers and our VoIP servers any day and at any time. .

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.