I’ve been playing Team Fortress 2 (TF2) for a while now and I found that there are a few things that could make the experience so much better. This is not a guide to teach you anything illegal. Everything that you can find here is perfectly legal and used by competive players and professionals.
The original HUD is not ideal for playing competitively. This is what you see without changing your HUD. Notice that all vital information is pushed off the the corners of the screen and when you have to take your eyes of the crosshair to look at those stats.
Previously, I used to use CommunityHUD when they included PVHUD. Since they switched to pure FlameHUD, I swapped to Garm3nHUD
Here’s some really good modifications to your HUD. The damage indicators next to your crosshair will let you know when you hit your target.
Most of my scripts are taken from stabbystabby. I recommend the flashing crosshair and null movement script. I have found the Viewmodel script to be very helpful when using the Ambassador. Here’s another good resource for scripts.
Null Movement script.
bind w +mfwd
bind s +mback
bind a +mleft
bind d +mright
alias +mfwd "-back;+forward;alias checkfwd +forward"
alias +mback "-forward;+back;alias checkback +back"
alias +mleft "-moveright;+moveleft;alias checkleft +moveleft"
alias +mright "-moveleft;+moveright;alias checkright +moveright"
alias -mfwd "-forward;checkback;alias checkfwd none"
alias -mback "-back;checkfwd;alias checkback none"
alias -mleft "-moveleft;checkright;alias checkleft none"
alias -mright "-moveright;checkleft;alias checkright none"
alias checkfwd none
alias checkback none
alias checkleft none
alias checkright none
alias none ""
Crouch Jump script.
alias +crouchjump "+jump; +duck"
alias -crouchjump "-duck; -jump"
bind "space" "+crouchjump"
Everything above lives inside the game’s own console configuration. TF2 ships a scripting system for binds and aliases, and competitive play has always permitted it, because a script automates your own input. It reads nothing and touches nothing. A wallhack reads memory the client should not show you. A null movement script cancels your own keystrokes. That is the line between configuring the game and modifying it, and everything in this post sits on the safe side.
In stock TF2, holding W and S together cancels out and you stand still. In a fight your fingers overlap on the keys more than you would guess, and every overlap is a full stop that ruins a strafe or a jump. The aliases fix it: when you press W, +mfwd runs -back before applying +forward, so the newest key wins and the old direction yields. The checkfwd family handles the release side, clearing state when both keys come up. The result is that the flick from one direction to its opposite takes effect on the first frame, which is what counter-strafing asks for.
Firing jump and duck on the same key presses both inputs on the same frame, and in Source that combination lifts your feet higher than a plain jump. It clears ledges, props and cart edges that would otherwise eat your momentum, and it shows up every thirty seconds of a match. Binding it to one key also means you never mistime the two inputs. The viewmodel trick from stabbystabby’s pack is the same idea applied to vision: the revolver model covers the center of the screen, and hiding it while aiming gives a clean sightline to the head you are lining up, while the crosshair stays put.
A HUD replacement is a set of vgui resource files that reposition and restyle the health, ammo, ubercharge and damage readouts. The competitive complaint about the stock HUD is that it pushes all of that into the screen corners, and every corner check is a moment your eyes spend away from the crosshair. Community HUDs pull the data towards the center in a tighter cluster, add damage numbers beside the crosshair so you know a hit landed without looking anywhere, and cut the decorative chrome. Garm3nHUD does this with a small footprint, which keeps the frame rate out of the argument.
Published on by Stanley