So who will be filling in for Ma3laa if he needs to demo due to Bdonski being MIA?

UVB is almost completely blocked by glass. UVA is partially blocked. UVB is what tans you, UVA doesn't really. So Phunk is right: you can't tan through a window. Both can cause skin cancer and skin aging though.

Glad I could help!

Can you zip hudammoweapons and hudlayout and clientscheme, upload it, and give a link? I'll take a look.

EDIT: also change fieldname of the shadow back to AmmoNoClipShadow. I just generally don't mess with those for default hud elements that I'm editing, in my experience they sometimes screw things up, even if it's just HudAnimations referencing the wrong element. Creates unnecessary troubleshooting.

I was just looking through the benchmarks thread and I was wrong, yeah, the benchmarks there indicate a 8~11% increase, my fault. I would still like to see benchmarks for his justification of Comanglia's stability over Toaster. Also would like an explanation on net settings, his logic doesn't make sense to me. At the least I think he should provide different sensible settings for people to choose from or test.

That will depend on specifications and setup, which is why I asked for benchmarks. Also your lack of network settings doesn't make any sense. Even if you have bad internet the default options are still horrendous. Also you made some claims that I would consider unsubstantiated: such as the no hats mod boosting fps. The creator of the mod claims it doesn't really and is mainly aesthetic. If it does for you I'd love to see some benchmarks. People always throw around tons of claims surrounding fps configs and peoples' computers always seem to have minute differences in what affects performance the most. Without actual proof for your claims I'm not going to switch from Comanglia's toaster config to his stability one, that doesn't make any sense, especially if your only justification is that it should run better.

Short answer: You need visible set to 0 and enabled set to 1.

Long Explanation: This is because it is not always visible but should always be enabled in case a class switches to a weapon without a clip, if that makes sense. In other words: enabled is, in short, if the element has the capacity to be visible, and visible is if it actually is or not.

Here's every combination of settings dissected: both set to 1 is for things that are always visible, like if you have a hud crosshair. Visible 0 and enabled 1 is what I just explained: things that are sometimes visible. Both set to 0 is disabled (sometimes this doesn't work though: if you're disabling something and setting both to 0 doesn't remove it try setting fgcolor to 0 0 0 0 or setting x or y pos to 9999). Enabled 0 Visible 1 would still be invisible because enabled overrides visible. Hope that helped!

EDIT: omni ninjad me but hopefully the explanation helps somebody.

do you have benchmarks in comparison to Comanglia's equivalent?

braided cords also break/fray much more easily in my personal experience. my old deathadder one just like stopped sending signals to the mouse at all. never had a comparable problem with a non-braided cord.

It's not really a huge issue to need to change to a different class when forward-spawning: if you use the scoreboard you can see which classes are currently in use and simply not swap to one of them. Even if you did misclick it's a two second delay. On the other hand, not having hard-coded class limits IS easily exploitable, at least by NA rules.

This is how that works in NA, and totally makes sense. Is it fair for a team holding last to have a scout switch to medic after their med gets picked and crit-heal buff everyone? Seems ridiculous to me and of course devalues med-picks. Without hard-coded class limits it would be easy for a team holding near a spawn (think on any last but granary or badlands valley) to have someone switch to medic a second or two before the real medic spawns, buff through the spawn door, and switch back, or heal the side of spawn that the medic won't be rolling out of, and the other team might not ever notice. Also let's say you're pushing last 2v3 vs a demo and 2 scouts, if you pick both scouts should their demo be allowed to play scout? Seems unfair to me, on certain lasts like gully it's basically having three scouts in the fight. Hard-coding it has objective benefits whereas leaving it up to player-discretion is easily abusable and debatable.

Kaneco has been handling bet verification and adding matches almost single-handedly all weekend, as well as helping with comp.tf and marking timestamps for the i55 video he's making. He and cherry and everyone I can see that has the permissions and knowledge to verify bets is asleep at the moment. I apologize if you wanted to use payout from that game to bet tonight but I'm unwilling to verify the bet at the moment as that can easily screw things up if Cherry is still applying fixes (and his last messages in slack indicate not to verify).

medic: pyyyour or knoxx
demoman: numlocked
pocket: yuki / mike
roamer: seagull
scout: clockwork
scout: sheep / enigma / b4nny

Anyone else have predictions for Day 2? Here's a blank bracket image if you want to do one.

http://i.imgur.com/1xf5fYu.png

https://saloon.tf/match/657/

https://saloon.tf/match/656/