@No1inPartiqlar That Clientscheme from idhud is up to date with the default hud and should make this work. If the font still doesn't show up, check if you have a custom "Resource/UI/quests/questitemtrackerpanel_base.res" and check the fonts/colors defined there (or just remove the file and use the actual default one)

Make sure the font QuestObjectiveTracker_Desc is defined in your clientscheme.res

@Flame you don't need to use #base at all, but for certain files it's easier to include the default one and just move things around, if you completely overhaul an element you can just provide your own .res file (or use that as the default for a #base include)

I duplicate them, just the actual name of the original value needs a visible 0 because it might be hidden by the new value you actually add to do the same job with a different color.

Having clear readable code makes it easier for someone else to maintain/modify, just good practice is all ;)

In the Scoreboard.res 'LocalPlayerStatsPanel' you have to duplicate each non-Label:

// Default 'Kills' (goes with KillsLabel)											
		"Kills"
		{
			"ControlName"		"CExLabel"
			"fieldName"		"Kills"
			"font"			"ScoreboardVerySmall"
			"labelText"		"%kills%"
			"textAlignment"		"west"
			"xpos"			"180"
			"ypos"			"0"
			"zpos"			"3"
			"wide"			"35"
			"tall"			"20"
			"autoResize"	"0"
			"pinCorner"		"0"
			"visible"		"1"
			"enabled"		"1"
		}

You copy the first 3 lines and then add a 'visible 0' and a closing curly bracket and add 'Value' to the 'duplicated section where you define a FgColor (foreground color) to change the text color like so:

// 'Duplicate' the name, fieldName and then hide it (visible 0)
// Add 'Value' in the names on the new element and change color
		"Kills"
		{
			"ControlName"		"CExLabel"
			"fieldName"		"Kills"
 "visible" "0" // Hide the original value that turns green
}
		"KillsValue"
		{
			"ControlName"		"CExLabel"
			"fieldName"		"KillsValue" // Add 'Value' here and to the name
			"font"			"ScoreboardVerySmall"
			"labelText"		"%kills%"
  "FgColor" "TanLight" // Change color
			"textAlignment"		"west"
			"xpos"			"180"
			"ypos"			"0"
			"zpos"			"3"
			"wide"			"35"
			"tall"			"20"
			"autoResize"	"0"
			"pinCorner"		"0"
			"visible"		"1"
			"enabled"		"1"
		}

----------------------------------------

Add a 'killstreak_image_width' in the scores section in the top of your Scoreboard.res file

"scores"
{
		"killstreak_image_width" "15" // Default value
}

----------------------------------------

The file you need to open is 'Charinfopanel.res' and then the BackgroundHeader & BackgroundFooter sections.
- Remove the 'image' and add 'fillcolor_override" "Black"

The continue might be a simplified textwindow.res (?), the map info section is:

resource/ui/MapInfoMenu.res

If you go on a local server and use the following in console when viewing the right thing in the hud you might be able to figure out certain files by the name of the hud elements:

sv_cheats 1; vgui_drawtree 1 // makes the vgui_drawtree show up
 vgui_drawtree_draw_selected 1 // similar to ticking 'highlight selected'

Finally someone who gets it :D

Increasing quality for the fat graphics, shiny particles and silly outlines Valve is forcing on you will increase your fps by stressing that beast of a GPU you have been keeping on a leash by redirecting every bit of load to your CPU by running potato settings because you came from a toaster.

FlameConfig-default when?! :D

Open and copy from the the default file the following and add it to RedPlayerList & BluePlayerList

"show_columns" "1"

This will make a grid for the columns show up to possibly figure out what does what. My guess for the 3rd column is that they're used for domination icons and killstreak + killstreak icon.

resource/ui/HudItemEffectMeter_PowerupBottle.res is the file you're looking for

Rawrsor, I'd recommend moving your custom animations with events to a seperate file, and leave the last line in the _manifest default to:"file" "scripts/hudanimations_tf.txt" so it is using the default file from the VPK. If there are events (for health/ammo colors) defined in the animation file you load in the manifest before the _tf file is loaded they will be used instead.

There is no need to mess with the actual default hudanimations_tf file if the manifest is set up correctly.

Ehm... If it has a clientside advanced option I doubt it has a serverside setting. You can disable the outlines for the server entirely though with tf_spec_xray 0 (replicated from server)

There is a bunch of undocumented Mann vs. Machine changes in the previous patch as well.

• Wave changes in what timeframe bot spawns on various maps
  
• Revive pod on Tank Barrier on Rottenburg doesn't disappear anymore
  
• When you lose less than 20 credits you still get a 50 credit bonus (previously 0 bonus for losing money)

Earlier in November someone stumbled upon this pastebin mentioning the taunts, possibly a campaign, new maps and more skins. Who knows it is actually happening!

Edit: I don't know why this got minus fragged, but info from the pastebin is actually true: Tough Break Update

D7S: Spectator.res and SpectatorTournament.res and then specifically the itempanel sections.

Go Back is bottom left, I would assume it's the 'trade with' button you have in your Armory overview, would suggest 2 crossing arrows like scrap.tf has

Find/extract HudDamageAccount.res and change the fonts there (delta_item_font = normal damage, delta_item_font_big = crits), also colors for healing/damage are changeable in that file.

LOL players using toaster settings on their beast PCs, increasing quality/texture settings has imho been proven to have decent frames than the shittiest settings on DX8 because of GPU offloading, especially on monster PCs.

Welcome to the wonderful world of TF2 with weapon skins, objective outlines for intel carriers/payload carts and player outlines when you're dead counting the frames!

Had fun complaining about Valve's inefficiency for their Build/Destroy menu panels when creating some for my HUD.

https://pbs.twimg.com/media/CU2tAZXWsAE-D17.jpg:large

The base files in the destroy_menu folder apparently are just there for show, repurposed those and basically removed 600~900 lines of code by replacing them with 2, which should work in all huds.