"TF_Welcome"					"Welcome Back, %playername%"

TF_Welcome is already declared to say welcome. Just change it to tf_rawrsor_welcome or something.

bball spec hud concept

http://i.imgur.com/P91ZL1f.jpg

It's really just look at the files, fiddle with them, try to make something, look at other people's huds and how they did it, ask if you're still clueless, repeat. Everything omni and collycat are pretty ordinary broken down, they're just good at combining the basic elements into something crazy nice.

What's most important is the game flows fine with it. Sure, things are balanced in the sense that both teams are equal, but that doesn't mean it's a good addition. You could make that argument over pretty literally everything, but here we are with weapon bans and whatnot.

Quickfix was dumb because teams weren't used to it. It's not a problem now, but it was back when it got buffed originally because people weren't aware of how to properly respond to it. I don't think anyone wants something similar to happen at i55 with a team rolling the competition solely because they've scrimmed with pickups more than any other team, even if that's a small risk.

A year from now we'll probably call ourselves dumb for disagreeing with medigun pickups. That's for i58 though, right now it's still a new mechanic that could potentially shake things up badly.

http://tf2.gamebanana.com/skins/137055
It used to semi-work in sv_pure 2 but it doesn't anymore.

Normally you can't have the labeltext be dynamic with additional text. So no "your health is: %health%" or anything like that, you're stuck with "%health%". For some reason it does work fine if you do that in tf_english though. "Padding" is really just doing something like "-%health%-" that way to cover both ends of it.

Getting buffed health to be teamcolored, that'd be simple since the green is just an imagepanel anyway. Low health because of it also acting like a healthcross wouldn't really be possible (with the way I did it, technically 100% health is "damaged" in order to get things to work, so you never get a color change you just get a healthbar). If I went with just plain numbers though, it'd definitely be possible.

I used type light (I'm poor), though this was pretty simple and any font editor would've been fine. The whole thing was a few days just to sort things out and tweak and whatnot, but just getting the font working took minutes.

That's pretty much exactly it actually. I just edited OpenSans and covered everything with a rectangle in the font (inverting it) so that it'd cover the surrounding area, threw it on top of a teamcolored imagepanel, and then edited tf_english to pad it for more/less digits or whatever making sure that the covered area extends past the healthpanel's edges. The background doesn't resize any, but at the same time it doesn't need to be a fixed-length font either.

It's easier to explain with a working example so here's the dl: https://www.dropbox.com/s/7567upgq58dfhgw/_HuevosHUD.zip?dl=1
To install you need to also take _HuevosHUD/localization/health.txt and copy what's in there to the end of tf/resource/tf_english.txt so that the labels work properly. I'm still trying to get something better working for this but I can't quite get something to do that automatically.
Keep in mind it's made for scout with the ammobar (full at 6, so a rocketlauncher would always be partially down since its max clip is 4) and it's far from done but it should work fine in any case. Disabling the ammobar wouldn't be difficult too and then it'd work equally across all classes.

working on trying some experimental stuff

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

more screenies

With developer 1 you could just filter everything you don't want out of the console with con_filter_enable 1;con_filter_text "some text that only appears in your echoes".

You can also make your own captions that only appear with the console command cc_emit "whatever the caption's named" but captions are a fair bit trickier to set up than echoes, though they do look a lot nicer. Clovervidia's guide is pretty good for getting started with captions.

There's some really roundabout ways to do if-then statements with aliases (null canceling movement script is the biggest and most basic example of this). I'm not really seeing where that'd be used in this so far though :B

The font maker decides the difference between higher/lower weights, it's not some unified thing. And I mean if you're the one making the font, you may as well make it work for outlines. I know from experience that fontforge can do it the way that would make outlines work, like in http://fontforge.github.io/Styles.html#Embolden

Some crosshairs are too thin to work/look good that way, but it'll still work with some and other methods like creating a second heavier font as the outline still work fine for all.

I think what he meant was having two font files, one with more weight but still with the same glyph size, not just changing the clientscheme size.

You can record a demo of them. Notifications can be triggered by spawning halloween bosses (such as with ent_create headless_hatman ) too.

http://tf2.gamebanana.com/skins/137388
I've always just used this. I've got an idea for something to try in the mod though.

All that could really be done to update clean tf2 for this would be to straight up remove stuff. Which I don't really want to do considering it still works fine on sv_pure 0 and it's the only thing keeping me from lagging. Basically, tf2 started using the shader that custom vmts use in sv_pure 2, while still trying to use the stock vmt's shader or something, which resulted in everything from working well for some materials to not displaying at all for others. Your guess is as good as mine for why this started happening but that's what I'm pretty sure's going on.

I doubt valve would leave it going on long if they see it though. A mod that's already spread around breaking and giving people half-functional wallhacks on sv_pure 2 sounds like the sort of thing they'd want to fix.

Just a heads up, if anyone's experiencing textures like in these screenshots (thanks fooqp), valve really messed up how world textures handle mods that change the shader probably accidentally, and now _unlit_world looks like this in sv_pure 2 with or without preloading.

It still works fine in sv_pure 0, but in the meantime I'd remove _unlit_world and/or _unlit_nofog_world if you plan on playing competitive or valve servers for the next little while. Nothing I can do other than advise for it.

Also sorry for the late replies but

Nofog removes the fog on textures at a distance. When textures that're far away are normally whiter and more pale from fog, they keep the full color with nofog. I'll be honest, I don't know which has a better impact on performance, since any difference I've gotten from it was within my margin of error (it doesn't help that my computer sucks).

A modded one got posted earlier,

I'm always thinking of more ways to do things, but right now I've got nothing.

Looks like valve fucked something up with shader-based mods. Admittedly, clean tf2 is the only shader-based mod I know of, but world textures are still sorta modded in sv_pure 2 even without preloading.

Textures that blend between materials disappear entirely, but past that I've got no clue what's going on. Some materials seem to be unlit like back before valve got rid of vmt preloading, some look like they're as shaded as they can be.

Is there any issues with the props? At least in my game, any prop in sv_pure 2 is normal, and sv_pure 0 clean tf2 works fully. I haven't seen anything bug out with them so far.

But yeah, removing _unlit_world or _unlit_nofog_world should fix this issue until valve patches/addresses it. In the meantime, I'd just send some emails to valve saying that mods of world textures that change the shader in the vmt is all fucked up. That's what I'm doing.