https://www.teamfortress.tv/22335/team-fortress-2-open-source
https://github.com/NicknineTheEagle/TF2-Base
https://github.com/danielmm8888/TF2Classic

click on the username to see the account details and the country name

getting both e30 and l30 is kind of a waste since the e30 already has a higher output power than most headphone amps

Actually the real number is 214748364.7% faster, because frametime (NOT FRAMERATE) is calculated in 32-bit signed integers which can only hold one less than 2 to the thirty-first power and it is measured in MILLISECONDS not percents. The fact you think this makes me think you use windows task manager to check your motherboard usage instead of the superior cmd command @for /f "delims=, tokens=2" %p in ('typeperf "\Processor(_Total)\% Processor Time" -sc 3 ^| find ":"') do @echo %~p% which does not diminish your team fortress 2 performance, and doesn't send telemetry signals to microsoft when used therefore not causing your dns to be resolved, also improving your ping

who

https://i.imgur.com/67p71oy.png

I recommend a Phalanx CIWS mounted on top of the control point with two short circuit engies taped to the sides

https://i.imgur.com/daSIvH3.png

https://i.imgur.com/UtXZgJm.png

try adding -textmode to launch options

Health kits respawn every 10 seconds, so if you take a medium kit every time it respawns for 30 minutes you could get 180 medium kits which would show as 360 in the logs. constantly rocket jumping between 2 spawns would make this pretty easy to get, and it's a lobby so you might not get kicked

You can treat rng in the same way as player inputs (which you can't predict), and the whole problem disappears.. even better if you treat the rng seeding as player input. Though it might be technically easier to synchronize the rng by having the server pre-determine the random results before they're needed, (ex. "the next time this scout fires the scattergun the bullets will come out in this pattern") and sending every client the info.

A much bigger problem may be that small hitches in the game's performance seem to have small effects on things like player trajectories. normal rng works deterministically and can be 'predicted', but predicting exactly how the engine interacts with every player's pc might be a nightmare

what about us skeleton boys?

You're free to fork it and maintain a version of mge free from the influence of people whose existence makes you feel uncomfortable

use net_graph 4 and take a screenshot of what it usually looks like when you're lagging, that might give some clues