Did you modify the VPK? Seems like its corrupted.

The problem I have with configs like this is that console variables aren't going to change from config to config. It's the same game/engine, reading the same console variables. So there's going to be ideal values for those variables that everyone will eventually find (besides the ones that control quality vs. performance tradeoffs). That means configs can only be distinct in their usage, like how Rhapsody's Config has aliases or how mastercomfig has a modular design/app.

If effort is just being made to find the right values, rather than make the config's usage different, then I think it would be best to build off of someone else's work and collaborate.

Hey guys, just wanted to give a quick update on mastercomfig. I will not be updating this config until Valve releases any information about the next major update (or releases the update). There's just a bunch of uncertainty in the investment I have to make to update the config, because everything could change in the next update and we just don't know what's going on in general.

Don't use this, it's broken and unmaintained at the moment, unfortunately.

I could calculate the rates manually myself. niko, could you tell me your up/down speeds?

These files were moved to the app folder. But you shouldn't be messing with them anyways, you can use tf/cfg/custom.cfg and tf/cfg/modules.cfg to override the app.

are you using mastercomfig very low? that disables a bunch of hud elements

add a _c to the class file name.

Try messing around with m_limitedcapture_workaround and m_rawinput

GAME 5 WOOOOO

liquid are gonna do it

Well what are your settings?

Please use r_lod -1 so that models in the distance have lower LODs!

You need to rename your class configs to have a _c. So like scout_c.cfg.

User info cvars are transmitted to the server. You can't create new cvars, only the user info cvar entries with setinfo.

Some of the commands removed were not doing anything in recent builds of TF2 and was verifiably able to test their uselessness. Others were those being set to default valies that were not flagged to be archived.

setinfo creates cvars with the user info flag. All cvars with this flag are sent to the server on join and cvar updates, which can bloat network communication and slightly increase client/server memory usage.

I'm so glad that this has come up. It's been a problem in our community for far too long for far too many people, including me. I'm happy that others have been brave enough to speak out and it's really encouraging to me, but I'm not sure if I'm ready yet to speak here about some of the harassment I've faced from some members of our community. Maybe I'll share eventually, but regardless, I hope that we are able to come to an agreement and stand in solidarity against toxicity. It's just common sense, and it will help us grow if we are open, friendly and inviting to all, new and old.