y'all need to stop comparing information leak bugs to mechanical bugs, it's embarrassing

that's not how that works

even if it was, here's a bunch of references in the code that clearly refer to this as *spectator* HUD elements
when you are alive as a character in a team, you are not a spectator

https://github.com/lua9520/source-engine-2018-hl2_src/blob/3bf9df6b2785fa6d951086978a3e66f49427166a/game/shared/viewport_panel_names.h#L22
https://github.com/lua9520/source-engine-2018-hl2_src/blob/3bf9df6b2785fa6d951086978a3e66f49427166a/game/client/sdk/vgui/sdkviewport.cpp#L75
https://github.com/lua9520/source-engine-2018-hl2_src/blob/3bf9df6b2785fa6d951086978a3e66f49427166a/game/client/tfc/vgui/tfcviewport.cpp#L86
https://github.com/lua9520/source-engine-2018-hl2_src/blob/3bf9df6b2785fa6d951086978a3e66f49427166a/game/client/game_controls/spectatorgui.h

hello, i am offering my help running LAN servers ^^

E: i completely overlooked they are working with PhoenixRed, i trust daalegard will set up great servers :)

i only tried one but it seems like they work :)

arie and/or steph found out that tftrue's tv_autorecord was causing the broken demos, so we haven't been using it this LAN

tf2-comp-fixes seems functional

Update does not seem to have affected the tf2-comp-fixes plugin, at least on Linux.

Did you try this? https://www.teamfortress.tv/59990/the-chat-box-keep-going-back-to-its-original-place

if it's the reflected detonator flare, how come it exploded? are you still in control of flares that got reflected? or maybe it was detonated the same frame it was reflected? either way, the high damage does not surprise me too much, self-damage calculation is busted on reflected projectiles

people are telling you it's a dog shit compromise in which legitimate players lose for no reason (it is)

#3 #6 This is part of the game.

#4 #7 #8 #9 I don't care

I wasn't expecting mostly feature requests for tf2-comp-fixes, but that's fine too. You might want to check issue tracker.

I've got a note for this on the tf2-comp-fixes issue tracker, however it felt low priority to implement compared to projectiles hitting friendlies: you have more chances to prevent that from happening on scout. I remember that you play a bunch of heavy, in which case I can totally see the issue being harder to deal with. I don't have a lot of time to dedicate to new tf2-comp-fixes features, but I'll keep it in mind for next time.

That's good to know, I'll make a note of it.

Do you have an example video/demo of that happening? I'll make a note of it as well.

When players run into annoyances, they don't always bring it up in the proper communication channels, and contributors may only pay attention to their own dedicated communication channels, leading to these small issues never being fixed. I don't intend to blame either parties, I imagine that both players and contributors prefer these annoyances be squashed.

Let's try something, you bring up the annoyances you come across while playing, and I'll try finding out what the reason for it, and bring it up to the respective projects owners.

I've started today:
The SOAPDM spawns on cp_gullywash_f5/f6 would often break on serveme.tf (This is the annoyance, this is what you report), however JaguarKing had provided new configurations to the SOAPDM project about a month ago, it turns out that only some of the serveme.tf installations had an outdated version of SOAPDM. That should be fixed now.

ultiduo players have been doing this forever. you are not cool.

kind of a sus question, kiddo

it is, and tf2-comp-fixes addresses this with the following feature:

the argument is that activating an ubercharge is a transaction that implies the complete consumption of the ubercharge, whether it's used efficiently or not.

with that plugin, the aspect of the dead ringer doesn't matter much.

the theory crafting about demoman stickies seems very silly to me.

VERY Excited about this! Cu@!!!

Not to my knowledge, no