To sum up my sources for this claim: Maps/Community servers/Steam invites can be corrupted in a specific way to execute programs on the client. As of now most of these RCEs have been patched by Valve in the CS:GO beta, but I cannot say the same thing for TF2 as we have no letter of confirmation from Valve.

Sources:
[1] - Remote exploitation of the Valve Source game engine
[2] - CVE-2021-30481: Source engine remote code execution via game invites
Here are some more sources listed (by u/QuodJaw)

Thank you! :)

In those cases a debugger might be needed (like GDB).

That situation doesn't always occur tho. Roamers are typically alone right? Also Solemn Vow allows you to see über too. (Remember that über can be faked with a voiceline!) While you can survive with calling damage numbers, you won't be able to get as much use out of them, as being able to see enemy health directly. There are a lot of advantages that calling health has over calling damage numbers, such as being immune to incorrect guesses from misleading movements.

Then just adapt to reduce the time spent looking at a player's HP. After all looking (or moving your mouse) in this game doesn't cost time right?

Cuz Unicode rulez.

Two overrated pillars of the medic META™.

Calling damage ≠ Calling health. e.g Calling "Demo took 50" means that demo can be from 50 to 210 due to overheal, while calling "Demo IS 50" simply means that demo is at 50. You'd be suprised how many times people lost simply because they guessed the wrong amount of health, since they tracked using damage numbers. That is why Solemn Vow is so useful.

Übersaw plays are extremely rare in comp, because they require too many conditions to be true to be worth it.

How so? According to the TF2 wiki, the Übersaw's attack rate is 0.96s (There is no additional delay since 0.96s is a multiple of 0.015). Medigun übers typically last eight seconds, so we can derive the consumption rate per second by diving 100 by 8; 100⁄8 = 12.5% über consumed per second. For reference the Übersaw's über-on-hit gives 25% über.

Since Übersaw's swing speed is 0.96s, we can safely assume that the total über will equal 12.5% after a second. Even ignoring the swing speed and only accounting for the base weapon switch speed of 0.5s, the consumption rate eats at 6% of the über-on-hit's 25%. Accounting for both the swing speed and base weapon switch speed (adds up to 1.46s), the consumption rate would be 18.25% über, meaning you'd only have 6.75% über left from the über-on-hit. All of this math assumes that decimals matter and that the über count isn't rounded.

TL;DR The über consumption rate does eat away at half of the über-on-hit and this is my proof. At the very least the über consumption rate eats away 24% of the über-on-hit's über and at worst it can eat away 73% über. Again this assumes that these variables aren't rounded.

And I'm here! Übersaw is just overrated trash. My posts sum up my reasons why. [1][2]

Amendments:

• Über chaining does not work at all; it requires the medic to abandon his pocket, which puts both at extreme risk, just to gain a few more seconds which are wasted anyways. Also the consumption rate eats away at half of the über-on-hit.
  
• Übersaw's taunt kill is useless. You get stuck in a single position which is dangerous and it's easy for the enemy to dodge the taunt kill.

edit: Lol I'm immediately downvoted as soon as I posted. Perfect! (Well I have 2 posts that still have positive votes so yay I guess.)

We might need to use the console logs to diagnose this issue. Do the following:

1. Go to the TF2 properties section and add the launch option "+con_logfile console.log"
   
2. Launch TF2 normally and play for a bit. Close TF2 after some time.
   
3. Upload the console.log file (located in Team Fortress 2/tf) and upload it to Pastebin.
   
4. Delete all contents in console.log (just do <select all command> -> <delete>)
   
5. Repeat steps 2 - 4 but launch TF2 through FACEIT instead. If it crashes that's fine; this is why we're using console logs.
   
6. Delete the "+con_logfile console.log" launch option afterwards.

How did you know my age and disorder?

Try preloading through the dynamic_background module (values can be itemtest or preload only if you have yttrium's viewmodel mod).

As for faceit, I doubt the mod would actually crash TF2. Exactly what did you install?

It's a hard punch.

Sry late reply. Anyway that's just one characteristic, which could just so happen to be someone remembering how to use a semi-colon. Also define "Willingly"?

Neither of those launch options are the problem. -particles merely determine the maximum amount of particles that can be shown (limit = launch option value * 512), while -precachefontchars just precaches the base character fonts.

The problem lies in the flame particles themselves, as they're buggy and laggy. As I mentioned earlier the Ultimate TF2 Visual Fix Pack fixes this issue.

The Ultimate Visual Fix Pack mod will remove the flame lag + patch other numerous visual bugs.