Can we talk about this point, I can definitely get behind transparency for all the unlocks themselves but this seems to be the major issue most people have with the whitelist. Only 31% of people actually want that (according to GentlemanJon's survey, 15% for the current whitelist and 16% for a very permissive one) with 62% against (40% shorter, 20% disliked things banned, 2% ban everything) with 7% (all those options suck) obviously not liking it but not necessarily being strongly against it.

Is there any particular reason this was done, or is this whitelist meant to be just some quick changes to the previous one with bigger changes still on the table for later?

Here's the proper ergonomics:

Basically just make sure you're able to keep a good sitting posture (back and neck straight), your arms are around a 90 degree angle from your body, but still elevated enough to keep your wrists above your keyboard and mouse. Even any one of those is more than most people do to avoid RSI so take it with a grain of salt, but I've started doing most of those and it feels a lot better.

None of my desks/tabletops I had supported this when sitting down, so I started using a standing desk, which is something to look into too.

Yes. Not because it's bad for ergonomics or anything, but because that sounds annoying as fuck.

I admit that I don't know much about the current election, but wasn't the main reason Macron and Le Pen became the two choices in the first place was because Hollande was pretty unanimously hated and screwed any chances of his party doing good, and Fillon was actually corrupt? Just seems like a shitty election in general.

The g300 isn't a consistent mouse. Offcenter sensor position, known jitter on many surfaces, potential positive or negative acceleration, and a 1.5 m/s malfunction speed.

I don't know enough about raw_input itself, other than that I've heard fps, fps inconsistency, and mouse hz can all have effects on its smoothness and input lag. But a better mouse will make a much bigger difference than raw_input would.

If a mouse sensor's native DPI is 800, you should use 800 dpi. If it's 1200 dpi, you should use 1200 dpi. This depends a lot on the mouse sensor in question, and nowadays a lot of sensors have a range for their native dpi (notably modern Pixart sensors) so it's more something you have to research.

Recommending it with a sens and not saying what mice makes it sound like the latter though.

it means save as all files so that it actually saves as a .cfg and not a .cfg.txt

But this guide is really old and outdated and you'd be better off just downloading everything from their actual threads. Comanglia's can be found here: http://www.teamfortress.tv/25328/comanglia-s-config-fps-guide

You can just tell by the order. The option that's the most popular will be at the top in the legend, the second biggest will be right under it, etc.

Even if you weren't having issues with color, you probably should just tell be the order anyway, since it changes for each graph (sometimes "a shorter whitelist" is the most popular making it blue, but in one graph it's the second biggest making it orange, and it's a little confusing).

I mean, the meta has been progressively getting slower and more stalematey, coincidentally as the crossbow kept getting buffed. Not entirely just the crossbow, the demo nerf slowed down the meta a low when it came out and the medic speed buff contributed when it happened, but there's a pretty strong correlation between crossbow buffs and a slower meta.

Not to mention etf2l's experiment with banning it in their cup seemed to be pretty positive that it sped the game up and made the meta overall better.

xbow is stupid but we don't need a 7th thread on it

Imo "this weapon is clearly only used to dick around with" counts as bad. Not "we need to ban this asap" bad or anything, but if we're changing the whitelist anyway then it's no extra effort at all to ban things that are only ever used to be annoying and nothing more.

But I think the whole point of the follow-up survey is to see what everyone thinks about exactly that.

That's why you keep getting asked "okay, but do you have anything to back you up on that?" What more thinking do we need to do first, if the opposing side isn't actually offering anything up other than "but are you sure?"

Well, we know its impact wasn't massively positive, otherwise we'd have seen a reversal in the team signup decline instead of it just getting bigger. So all that's left is it's either negligibly positive, not impactful at all, negligibly bad, or significantly bad. Which means we either aren't really losing anything by changing the whitelist and don't need to worry, or we're actively improving things when we do.

That's fair, and that's what I've been arguing too. I think useless weapons should be banned personally, and I've laid out my reasons why I think so. If you think they should be allowed, that's completely fine too. But the point I'm making here is that I disagree with you that banning useless weapons is some sort of huge risk that could potentially have big terrible consequences to team numbers.

What I'd like to see banned is anything that overall has a clearly and demonstrably negative impact on the meta / how the game is played / how enjoyable it is (in other words, actively bad weapons), or weapons with no positive impact to speak of and no usage numbers in competitive to justify it (useless weapons).

I could make a whitelist and you could nitpick it, but ultimately it comes to those two categories being banned. That's still a lot of weapons, but don't think anyone's trying to argue for a 3-item-whitelist or anything like that.

It's sorta already implemented. hud_damagemeter is a console command that shows your DPS, and the time can be changed by hud_damagemeter_period 60 to show DPM instead (might need to mess with hud_damagemeter_ooctimer too), but unfortunately it's locked by cheats.

I'm not responding to everything, both because I don't want another huge wall of text, and because these few points cover most of your post.

"We don't know for sure, so we should do nothing" is a terrible approach. All the information we have points to it having done nothing good. We have more information now than we did when we decided to start unbanning everything, at least. If you need more assurance that it will or won't work, you can always start polling reddit or go ask every low open player or whatever, but the information we have is enough to go off of imo.

Sure, overwatch is probably a way bigger factor, but if all that means is the whitelist's impact is negligible then we don't need to worry about "shrinking the community" from changing it. In that case we can do pretty much anything we want with it, because how much it changes the community size is a non-issue then. It's either not very significant, in which case we shouldn't worry about changing it, or pretty significant, in which case it failed horribly and we should change it asap.

I'm not saying we deserved to win, and I'd be telling that story even if we ended up winning by the end of it. That's not the point, the point is that it was effective. It switched directions of a hard roll because it was just so different than anything we'd encountered before, not by them playing smarter or fragging harder but by doing a retard strat.

I agree, and for that reason I'd like to see them included (tentatively, because I'm not sure if those strats are actually fun and non-bull, so I'd go with more experienced players' opinions though I'm not against the idea). What do you think I've been arguing, "if it's not gunboats it's banned"?

I'm just saying, the only times I can remember the community being wrong about balance is when problems get exaggerated, but those same problems do still exist within the game to some degree more than they benefit the game. And I don't think it's really a problem to work off that since how big the issue is might be off, but there's still an issue with them. We, as a community, tend to be pretty good at this stuff. You're free to provide counter examples though.

Not disagreeing, but there's also the many crossbow buffs which definitely have changed the meta. The big arguments are how much it changed it, if the meta change was good or bad (though most people seem to agree that it was bad), and if it's bad enough that it should be banned.

The other thing is that, whether through inexperienced players not knowing how to counter it or sandbaggers dicking around with it, this does sometimes happen at low levels. Sure, if a weapon never got used then it doesn't matter if they're banned or not, but they are used (even if it's not at the level we play or watch). So how do we approach that, should we leave them unbanned so that new players learn to deal with it, or should we ban them so that the issue never comes up at all? If a "useless" weapon is only ever used to mess with people, is that reason enough to ban it, or should it be on them to get better and win against it?

I think we should just ban them and be done with it (though really I'd be happy with pretty much any stricter whitelist), but the only reason this thread's 9 10 pages long is because a lot of people have a lot of different views.

You'd want them to have the same values as the non-minmode. At least, the xpos values so that it's centered, if you don't want anything else about it changed.

Or you can just ctrl+h replace-all "_minmode" to "_minmodeDisabledOrSomething" so that the minmode parts stop working and it doesn't care about them at all. Or, if it doesn't change anything else about the hud, you could even just turn off minmode in tf2's options. Those are only if you're fine with any other changes though.

Map editors can include an env_fog_controller. I don't know all the details but I'd assume that'd be required, it's just that it's common practice to include it in most maps/maptypes.

It would make sense for jump maps to not have them, since jump maps don't tend to go for visuals (or when they do, they're a lot more abstract than actual tf2 maps).

Could you just decompile, add an env_fog_controller, recompile under the same name, and then load the demo with that, or is there some signature check that'd screw that up?