http://www.dodbits.com/dods/index.php/source-graphics/source-gui-hud-tutorials/33-console-font-color-and-size

If you're fine with reloading the hud when you switch classes, you sorta can.

The easy way is to setup each class cfg to run either cl_hud_minmode 0 or 1, and make the HealthDeathWarning depend on that. The obvious limitation being that there's only 2 colors to pick from, and you can't use minmode for anything else, and reloading the hud via cl_hud_minmode will make switching classes take up some extra time (if your computer's good it'll be pretty small, if it's bad it'll be killer).

There is a way to make all classes have a different hud, but it involves each class cfg echoing a #base to the class specific files and logging that to a .txt file that itself gets loaded by #base by hudplayerhealth.res, and then reloading the hud so that the #base gets used. Bigger limitations, because that file has to get flushed out frequently (wouldn't be an issue if you could log to the top of a file, but you have to append unfortunately). Much harder to get working and with much bigger limitations.

Otherwise, there are no known ways to get class-specific huds, and I'd suspect any way of finagling the health panel itself to do what you want without the above would be orders of magnitude harder if they're even possible.

I could only read it as him saying every position you can hold is stupid.

• If you are vegan, then the only reason you're following a personal moral code and don't want to do things you consider unethical is because you're a narcissist.
  
• If you are against vegans, then you're just a part of a stupid circlejerk.
  
• If you are fine with most vegans, then you're a normie.

It somehow manages to act smugly superior to vegans, while calling out people who act smugly superior to vegans (and anyone who realizes that not every vegan is awful).

I think the main arguments are:
- increasing demand, even if you're buying from good sources, will make producers increase supply and a lot of that will come from places that don't care much about animal rights / those good sources may have to compromise in order to ramp up production.
- even if the animals are treated well, the idea that they're selectively bred, born, and raised solely for people to eat/use doesn't sit well with some people.

I eat meat too, and don't take a personal issue with either, but I can understand why they'd feel the way they do. Of course you also get some idiots that think farms are abusive for fun or other nonsense, but all the vegans I've met in real life are completely rational about it.

You can preload cp icons reliably but the majority of things don't work with it.

As far as I know there is no current way to add custom class icons to the spectator hud in sv_pure.

You can simplify the script with incrementvar like so:

bind mwheelup "incrementvar demo_timescale 0.1 10 0.1"
bind mwheeldown "incrementvar demo_timescale 0.1 10 -0.1"

It does make it a bit more inflexible than with aliases--can't make something happen when you hit the min/max or make it wrap around or anything, but it works fine for this.

Just to elaborate, one of the maps (rocket shooting iirc) sets it to mat_fullbright 1 and it never gets set to 0 so it stays when you go to other maps. But it requires sv_cheats 1 to work, which public servers usually have turned off, so it won't work on servers.

And by clean tf2 being broken in sv_pure, it means some textures being fully bright, some being completely dark, and any blend texture (most dirt / ground) is completely invisible. It's fucked, basically. I've been working on a new version but haven't gotten any workaround for that breaking.

A lot of people would probably use voice chat, but it's always good for new scripts to be made. I do remember hearing about a mute (maybe deaf? can't remember) player who would use a script like this, since they needed it for callouts.

If you want to add to the script to do more, it's easier. For example, if you wanted to change the script so that it prints everything out on one line (but requires multiple keypresses before it prints anything):

// commands to re-alias
alias leuxd_say_0 "leuxd_say_0a"
alias leuxd_say_1 "leuxd_say_1a"
//...

// first keypress, switch to different modes
alias leuxd_say_0a "alias leuxd_say_0 leuxd_say_00; alias leuxd_say_1 leuxd_say_10"
alias leuxd_say_1a "alias leuxd_say_0 leuxd_say_01; alias leuxd_say_1 leuxd_say_11"
//...

// second keypress, say different things
alias leuxd_say_00 "leuxd_reset; say_team UBERED SCOUT"
alias leuxd_say_01 "leuxd_reset; say_team UBERED SOLDIER"
//...
alias leuxd_say_10 "leuxd_reset; say_team INJURED SCOUT"
alias leuxd_say_11 "leuxd_reset; say_team INJURED SOLDIER"
//...

// additional logic
alias leuxd_reset "alias leuxd_say_0 leuxd_say_0a; alias leuxd_say_1 leuxd_say_1a"

// the binds remain the same as before
bind "KP_INS" "leuxd_say_0"
bind "KP_DOWNARROW" "leuxd_say_1"
//...

That's one of the main reasons that using aliases, even when you don't need to, is a "best practice." It just makes things easier when you want to change it later.

people always say this but they are intentionally implemented features, that the game is balanced for and good maps are designed around. I've never heard of a map designer intentionally making things wallbuggable.

It would be pretty hard to 100% ban considering how easy it is to accidentally wallbug. But I don't see why you couldn't only go after blatant abuses with some rule about "intentionally waiting for x seconds" and/or "standing still on the skybox" or something along those lines.

bind "NUMPAD0" "say_team INCOMING"
bind "NUMPAD1" "say_team MEDIC"
bind "NUMPAD2" "say_team DOWN"
bind "NUMPAD3" "say_team UBER"
bind "NUMPAD4" "say_team PLEASE"
bind "NUMPAD5" "say_team HELP"
bind "NUMPAD6" "say_team SPY"
bind "NUMPAD7" "say_team ATTENTION"
bind "NUMPAD8" "say_team ENEMY"
bind "NUMPAD9" "say_team IN OUR BASE"

The binds should be:

bind "KP_INS" "say_team INCOMING" // 0
bind "KP_END" "say_team MEDIC" // 1
bind "KP_DOWNARROW" "say_team DOWN" // 2
bind "KP_PGDN" "say_team UBER" // 3
bind "KP_LEFTARROW" "say_team PLEASE" // 4
bind "KP_5" "say_team HELP" // 5
bind "KP_RIGHTARROW" "say_team SPY" // 6
bind "KP_HOME" "say_team ATTENTION" // 7
bind "KP_UPARROW" "say_team ENEMY" // 8
bind "KP_PGUP" "say_team IN OUR BASE" // 9

As per https://wiki.teamfortress.com/wiki/Scripting#List_of_key_names

Alternatively you can make it easier for the user to rebind it by doing something like this:

alias leuxd_say_0 "say_team INCOMING"
alias leuxd_say_1 "say_team MEDIC"
//...

bind "KP_INS" "leuxd_say_0"
bind "KP_DOWNARROW" "leuxd_say_1"
//..

If lawena doesn't cover it, the easiest way would probably be to go into scripts/hudlayout.res and make everything other than the damageaccount panel and the deathnotices and use:

"xpos" "r0"
"ypos" "r0"
"wide" "0"
"tall" "0"

Which will get most things, and then do the same in whatever straggler file you find (like resource/ui/hudplayerhealth.res).

Both are possible, but are very far from easy.

For 1, you can change the bonuscross to be a solid material (the same as the bg, or a refract material if you want no bg), and have position that at the left/right of your hp bar, and then set it to scale so that when at 0 health it covers all of the hp bar.
For 2, you can make the hp bar that gets covered by 1 use a complicated mess of custom fonts, that are block fonts but set up with the label width so that it only appears when health is 2 digits or whatever. You can do it more complicated with weirder custom block fonts that appear at arbitrary values, but going by digits is significantly easier. And though I've never done it myself, you could hypothetically pin_to_corner to the max health number with a special font (and set that to use auto wide to contents) to let you differentiate between different max health values and recreate percentages.
Magnum hud does both in a way (except for #1 it is positioned upwards and scales towards the bottom, and for #2 it only cares about health values >100 and >50 and >10 and so on without dealing with percents), if you need a reference.

Needless to say, it's probably much more work than it's worth.

Iirc it uses the same font as the rest of the killfeed. To make it smaller you have to edit the TextFont used by HudDeathNotices in hudlayout.res, whether by just swapping it to use a smaller font or changing the font declaration in clientscheme.res.

I can't remember if killfeed fonts overlapping icons is a size issue or a font kerning issue though. It might require either using a different font, or manually editing how the kerning on that font works, in order to solve.

I feel like there could be a lot of breaking changes if #base was accounted for, ie. two unrelated files using #base on the same file, and stock hud updates it in one location but it would break if added to the other.

If a hud fully uses #base it'd be effectively be doing this anyway though. I'm more wondering about if it can keep track of any intentional removals (most huds removal all minmode values for example) when updating. e: specifically mentions that these need to be null'd out, for anyone wondering

You can edit the vtf file in paint.net with the vtf plugin:
https://www.getpaint.net/
http://nemesis.thewavelength.net/index.php?p=50
Or photoshop with the vtf plugin if that's more your thing:
http://nemesis.thewavelength.net/index.php?p=39

As far as I know, they are all:

PIN_TOPLEFT
PIN_TOPRIGHT
PIN_BOTTOMLEFT
PIN_BOTTOMRIGHT
PIN_CENTER_TOP
PIN_CENTER_RIGHT
PIN_CENTER_BOTTOM
PIN_CENTER_LEFT

Those are all just aliases for numbers though, and "pin_corner_to_sibling" "1" or 2 or 3 or whatever is entirely functional.

http://www.dodbits.com/dods/index.php/source-graphics/source-gui-hud-tutorials/34-change-the-netgraph-font-size

memes aside -- making an fps config is very difficult and takes a lot of effort. Mastercomfig has over 2 years of work put into it, and is several thousand lines long in total (compared to your 38 lines long). Unless you do something completely different (rhapsody's had an in-game setup, for example) and spend as much time and effort making something equally good, there's no reason to not just use mastercoms' instead.

Not to discourage you from contributing to the community, but making a good fps cfg is not an easy thing to do.

Also worth noting that sourcecode for tf2 is from 2008, and a lot of things have changed in the decade since (iirc explosions were turned from cubes to spheres in 2009, for example) so you have to take it with a grain of salt.