Got bad (no) file permissions for non-root when installing from mastercomfig-app-7.0.0-a.10.pacman, simply chmod my install. The .tar.xz is fine.

From testing, it seems "mat_texture_reload_frame_swap_workaround 0" fixes the problem. I'm running Arch Linux / amdgpu // Ryzen 1600 (3.8 Ghz) / 3200Mhz 2x8GB RAM / RX 580 4GB.

FPS gain/loss seems negligible with either option so I set it to 0 in custom.

alias.cfg:

Launch: -novid -noassert -nojoy -nosteamcontroller -softparticlesdefaultoff -reuse -NoQueuedPacketThread -nostartupsound -nohltv -threads 8 -gl_enablesamplerobjects

heavyweapons_c:
viewmodel_fov 100
alias class_set "alias class_last join_class heavyweapons"

game_overrides_c:

custom

I have a similar issue to Owen's: my game temporarily freezes after I select Heavy, for whom I have the most tame _c config. This tends to occur once after each map load. The freeze does not happen with -default or with mastercomfig removed.

The repo was split up. Here's hudanimations_tf.txt. IIRC you can make an event with just braces in your custom animation file to disable it.

It is functionally the same (no splash fall-off, unless boosted oddly enough, and huge knockback), but yeah, it is not as exciting without the extra bits :( .

@Tsarbucks, as Cubekoi stated, you should have most everything.

I also have a stock HUD repo (config files only), with additions/removals described in the linked wiki page.

For updates, I recommend following huds.tf and/or this tracker (feed).

@Koncept, try

tf_disguise_menu_controller_mode 0

If you are using a controller, I do not know if using the mouse+kb menu breaks your ability to disguise.

If you need to modify the controller disguise menu, most of the files you need to tinker with are in /resource/ui/disguise_menu_360/ or /disguise_menu_sc/. Search for guides on how to edit a HUD - it is easy. As for stock files, you can dl from the repos shared above. If you want to reposition the disguise menu (or even move it offscreen to hide it), see "HudMenuSpyDisguise" in /scripts/hudlayout.res.

@XenThePybro #3852: basechat.res is packed in /Team Fortress 2/hl2/hl2_misc_dir.vpk. I'm not even sure if it has ever been touched for stock HUD changes. Here it is in my repo.

@JB #3854: Try looking at the questitemtrackerpanel* files in /resource/ui/quests/.

@Lyreix #3853: Following XenThePybro #3855, you likely have another TargetNameLabel, perhaps named TargetNameLabel2, TargetNameLabel_ or similar. If you want to keep floating health, you can try pinning that extra label to TargetNameLabel by adding the following to that extra label's section:

		"pin_to_sibling" 	"TargetNameLabel"
		"pin_corner_to_sibling" "PIN_TOPLEFT"
		"pin_to_sibling_corner" "PIN_TOPLEFT"

It is in matchmakinggrouppanel.res, "BGPanel". I'm fairly certain it is not one of those random, stubborn HUD elements, so you can do what you want to it.

As far as I know, the bonus charge never applied. I had posted on the wiki page's talk page a week after the update.

I wonder if the change was considered but ultimately not released, and by mistake it made it to the patch notes. It was not in the item's in-game description, and I do not recall the bonus ever appearing in items_game.txt either, but it could be hidden in addition to being broken.

I think feeling it out is sufficient, and when someone needs finer details, finding an article or asking another player isn't too much of a burden. I can't recall information that is still mostly hiding in an old patch note or blog; players do cite those pages when informing others, but I admit they seldom turn up at the top of search results. It is unfortunate when that is the case, because the info can be made more accessible.

Most of the SBL's properties can be discovered by players with damage numbers enabled (I'll admit this statement seems optimistic, as most people I know believe they are above-average). At minimum, players should know that charged stickies are useful for extra distance. With damage numbers, players should definitely realize that charging does not add damage to stock stickies, and that after some time, stickies deal more damage at a distance. Some might even notice that traps deal less damage when camping close to an entrance. The decrease in damage with reduced radius is small enough that it probably continues unnoticed until a player frequently connects airdets about its edge, but players should discern that stickies deal more damage at the feet (granted, for additional reasons).

Some other mechanics that should flick on light bulbs when revealed include: crit heals, ubercharge rate (at least when paired with another heal beam), disguised spies being immune to most knockback, larger knockback while mid-air/crouching, and of course, melee random-crit chance.

Some things are harder to discover alone, such as disguise smoke, mini-crits being linked to the player or how to airstrafe better. One of the most frustrating experiences for me was testing and learning about the clusterfuck that is the on-hit effects against ubered/bonked/cloaked/disguised/cloaked+disguised players, and the dead ringer. Valve should clean up those interactions so they're easier to learn in normal play.

Although wikis and guides exist, I agree that more details need to be in-game, if Valve wants players to improve a bit faster. Updated tips and item details, and easy access to them in-game would be nice, particularly for new players that do not have many items. Still, the bulk of learning the game should, and already does, come from first-hand experience and the community, as opposed to static documentation.

Regarding complex weapons, I do fear the possibility of memorizing damage/effective health tables becoming more than trivial for decision-making. There might be a peak where Valve adds the ability to see or even batch ally damage, or make enemy IDs visible for all players, just to recover some quality of life when damage output becomes ridiculously volatile.

My repos' diff.

Whoever posted data for the Original probably took the minimum interval between firing a rocket and firing after reloading a rocket.

It is useful information, but not very useful for some cases, ie. manual reloading or switching weapons. For example, if the RL clip is emptied then another item is held for a while, it should take ~0.9s to reload and fire a rocket after switching, so a rocket can be fired ~1.4s after switching back to RL.

Regarding damage, it could simply be old data. With damage spread, max fall-off is 50%, and it still is, but nospread is the default setting now; the way nospread works caps normal weapons at ~53%.

vm_* are aliases, in the second block of my script. My script is customized for classes via redefining them in class cfgs, as in the example. You can add more commands as you like within the quotes, with semicolons (;) separating them.

I don't know the commands for xray and cart glow, but you can search online or use "find" in console, eg. find xray.