https://i.imgur.com/B8CkU1o.png

https://i.imgur.com/3OwJABY.png

That wouldn't be fullbright, that'd be the flat textures messing up how they're generated (which I'm still looking into).

Fullbright will still cause (different) issues in sv_pure 2 though and afaik there isn't much I can do about that

Alternatively just don't use the resize option. If it doesn't get resized, it won't look like this in sv_pure and will just be the default textures.

Some will (nohats, for example), some will look different (flat textures with resizing, see above), and some won't (flat textures without resizing).

Haven't been able to make as much progress as I'd have liked, but two of the more interesting things I've done so far:

https://i.imgur.com/x0CnDQC.png

blur shadows aren't too uncommon anymore, but gradient text is still pretty unique -- trying some soft gradients with this one and think they turned out pretty good.

https://i.imgur.com/VPGR9KJ.png

both types of the killfeed using white icons, means the background can be the same color (and just change their transparency). Internally this is done using colly's killfeed icons, except the mod_textures.txt is redone to be update-proof and somewhat cleaner.

You go to a casino slot machine. It has a software error that means you win big every roll, instead of once in a hundred rolls. You, and thousands of others, try to do this as much as possible before it's patched since you fully know it's an unintended exploit. A casino employee notices this and points to the disclaimer on the machine saying "in case of software error, winnings are voided and payments refunded." You don't get the money that you shouldn't have gotten in the first place, and act like you were the one ripped off when they didn't let you abuse their system.

This is also what actually happens in these cases: https://vegasclick.com/games/slots/malfunctions
Valve would have an even stronger case because it's all virtual hats inside their own service, and they reserve the right to do whatever they want with your items.

Probably revert what they can and hand out an item, for everyone's troubles. The cheater's lament got mentioned a few times, but they also did it with the glitched circuit board. It was never as extreme as this, but it's not the first time they've had to deal with people getting items they weren't supposed to.

Glad to see another, always fun to compete in contests
Getting everything in rule 3 is gonna be a lot but I don't think it'd be too bad with some borrowing from other huds

Bold of you to assume everyone's played mann power

There are a lot of good options: ducky, coolermaster, filco, pok3r, etc. And lots of groupbuy / custom keyboards if you're looking to splurge or DIY some.

Switches are mostly preference so what exactly are you looking for that razer green switches didn't offer? More/less tactile, more/less clicky, etc.?

While it's bumped I did do some writing on this: https://github.com/JarateKing/jarconfig/blob/master/docs/zoom_sensitivity_ratio.md
It's the same conclusion (0.793471 is what you probably want) but explains some of the thought behind it.

Yeah it wouldn't be too hard. Throw this into wolfram alpha:

(arctan(x*tan((20 * pi/180)/2) ) / arctan(x*tan((90 * pi/180)/2)))/(20/90) = 0.83333

And replace "0.83333" with your tf2 zoom sense. This should give you an x value, then throw this into wolfram alpha again:

(arctan(0.403109*tan((40 * pi/180)/2) ) / arctan(0.403109*tan((90 * pi/180)/2)))/(40/90)

Replacing the two "0.403109"s with the x value from before. The result should be the same zoom sens.

quick python script for this:

# range to set
min = -2
max = 2

# enforce proper wrapping rules
def getCoords(x, y, z, separator):
    toret = ''
    toret += str((x - min) % (max - min + 1) + min) + separator
    toret += str((y - min) % (max - min + 1) + min) + separator
    toret += str((z - min) % (max - min + 1) + min) 
    return toret

# base binds
for c in ['x', 'y', 'z']:
    print('alias "inc_vm_' + c + '" "vm_0_0_0"')
print('')

# internal state binds
for x in range(min, max + 1):
    for y in range(min, max + 1):
        for z in range(min, max + 1):
            toprint = 'alias "vm_' + getCoords(x, y, z, '_') + '" "'
            toprint += 'tf_viewmodels_offset_override ' + getCoords(x, y, z, ' ') + ';'
            toprint += 'alias inc_vm_x vm_' + getCoords(x+1, y, z, '_') + ';'
            toprint += 'alias inc_vm_y vm_' + getCoords(x, y+1, z, '_') + ';'
            toprint += 'alias inc_vm_z vm_' + getCoords(x, y, z+1, '_') + '"'
            print(toprint)

There's some obvious big improvements (support for decrementing instead of just having to wrap around, and support for floats / not having to always be an integer) but this should get the idea across.

What huds are you trying? If they're old, then their info.vdf files probably aren't up to date (if they have one at all).

In the future, there's https://www.teamfortress.tv/19073/hud-editing-short-questions-quick-answers

Copy over HudDeathNotice inside scripts/hudlayout.res

Might also need to copy over fonts and colors from clientscheme to do it but should be easy enough to do with some know-how about the clientscheme:
https://github.com/JarateKing/TF2-Hud-Reference/blob/master/0-TUTORIAL/3-Editing-Clientscheme.md

Specifically, you just need a label that has the labeltext "%metal%". Anything else doesn't really matter, it's just a regular label that you put in huddamageaccount.res.

None in sv_pure. You can edit the vmt/vtf to change the images, or the .pcf to change the particle effect itself, but in both cases it'll revert to default in sv_pure. Don't have the filenames on hand but shouldn't be too hard to find them either.

So far it's helped me with my last two jobs. The interviewers for my current job were impressed with the tf2 stuff on my github (even though they had no clue what tf2 was), and my previous job was a gamedev position where experience modding games was a big asset. These are both programming jobs so a lot of the skills are transferable, but in both what sold it was the things I've done in tf2.

I also fucked up another game programmer interview by talking too much about my tf2 mods and not enough about my other experience, but it's been more wins than losses so far.

Just a note: chat_english will not run into these issues. tf_english will, and for that reason it's recommended to use chat_english for any localization changes.

Try (re)installing the fonts. It's pretty hard to tell what the problem is with just that, but if it's just the font files not getting transferred / recognized then installing them means the clientscheme doesn't have to reference the local copy.