There are other versions that don't, such as:
http://www.teamfortress.tv/12706/help-with-flat-textures

Though iirc it's more outdated and has a much larger filesize.

Can't you just create a second label with %targetname% as the labeltext, and set the original TargetNameLabel's alpha to 0? Can't really test right now but you'd keep your bg the same color that way.

if you shoot someone sometimes it'll kill them sometimes it'll just hurt their leg
idk

How?

Ban = showing valve we don't like it = there's some issue with the weapon = eventual nerf or rework
No ban = not showing valve we don't like it = for all they know it's fine = no change

Valve doesn't browse tftv or anything, banning weapons would be dumb if we had direct communication with valve and never needed to ban things, but weapon bans are our only surefire way of highlighting "this weapon is a problem" (and doubles as a temporary solution to it too).

I'm not necessarily saying the loose cannon deserves to be banned, but avoiding bans entirely to try and show what's wrong with items is the opposite of what you'd want to do.

This is all theorycrafting but at least with my understanding, nothing'd stop you from using custom sounds for anything, assuming you get the game_sounds_something.txt files to properly and reliably load to do what you want.

Sv_pure no matter how many times it says whitelist is at the end of the day actually a blacklist that only fully blacklists a few folders, so a sound would still "work" in sv_pure if it's inside a folder like scripts or resource or literally anything that's not sound, models, materials, or particles. The only issue is that if it's there, it's not replacing anything, so you'd need game_sounds to reliably work to replace things (where you can just add ../ in the specified file location to bring it outside of the sound folder and use a sound from literally anywhere).

I experimented with doing basically the same thing with materials before vmts stopped preloading (despite there already being replay/thumbnails/, I wanted to see if I could, and I could). My experience with game_sounds is really hit-or-miss and I personally don't want to mess with it much, but if someone figures that out then you should be able to do whatever, unless I'm missing something key.

Probably going to be patched at one point or another but eh.

You can change it to any sound that's found within any of the game_sounds.txt files found in the vpk's afaik. It doesn't necessarily have to be copied over from another one of the ctx files.

The original sounds for example would be changing Weapon_RPG_DirectHit in the example to Weapon_QuakeRPG.

edit I'm dumb, this is the other way around. This is how you get the list of every sound that's usable though, by checking in game_sounds_something.txt

what would happen if aim posts and it gets more than 125 minusfrags?

http://i.imgur.com/yNwT14C.png

UPDATED CLEAN TF2
-added _clean_waters, which makes water look like the above and should help fps by a fair bit on water-heavy maps
-split _unlit_playermodels to make _unlit_weapons too
-added _unlit_weapons_noskins to remove the gunmettle skins from weapons (bit late coming, sorry bout that)
-reorganized everything to go into subfolders based on how they work in sv_pure

_clean_waters messes up a bit in sv_pure 2, much like _unlit_world now does, but I'm keeping both included in any case
I don't have any stattrack weapons to test it on so unfortunately _unlit_weapons_noskins just gets rid of the skin material, but should be fine 99% of the time.

My friends think I must be winning thousands of dollars all the time because of comp tf2.

Here's where you should ask hud questions: http://www.teamfortress.tv/19073/hud-editing-short-questions-quick-answers
Looking there's helpful too, since odds are it'd have been asked before.

You linked the results of the strawpoll, not the strawpoll itself. Just saying.

Fair enough, but for:

Losing the round/needing to hold last against an uber with nothing is pretty severe for dying a bit forward/not already backed out when they push, which happens to every medic, even if you'd like to see medics get punished more. Basically ensuring you're going to die if you really go far forward, and losing uber advantage if you die no matter where you are is enough for me.

We already know what's wrong. It's way too severe, and brings in huge problems for next to no upsides. The most meaningful data we could give to valve is that there's only one league that doesn't have it banned completely, and judging by that thread aporia linked, they don't want it around either.

If the medic's dumb he might run in, but in most situations where you won mid, you could clear out the enemy team from mid in less than 15 seconds, and when you can't it's better to keep your med alive anyway.

All this would really change is it'd stop picking up your own medigun, but the bigger issue between the two choices is picking up the other medic's medigun. If the dead medic can't pick it up anymore, then the alive one's no worse off if he doesn't take it, so it either does nothing or snowballs just as hard as before.

You might be able to call that a step in the right direction I guess, but you're arguably punishing medics harder for dying since they can't pick up their mediguns again, while all their out of position deaths still give the other medic uber, with no real reason to have any of that in the game in the first place. Setting the decay time to 0 is still the much better option, all that comes from medigun pickups the way they are is bad no matter their despawn time.

rayshud

https://www.teamfortress.tv/7598/tf2-benchmarks
Got any benchmarks/comparisons?

edit: ninja vipe