they've been banning sold accounts, hopefully that doesn't happen to you

seagull had one of the character designers (morello) in a voice call: https://www.twitch.tv/videos/592871001?t=6h36m35s
didn't listen closely but a major red flag popped up, they don't want deterministic spray patterns (not random, learnable) because "spraying vs tapping should be an important decision"
the guy sounds like a redditor too which doesnt really help (legit said big chungus at some point)

asking SIGSEGV for some pointers, if it's nothing extraordinary, i'll try making a plugin
next, and that's on you, you're gonna have to ask who will accept running it
serveme most likely wont if there's no tangible reason to, although arie is very nice and reasonable
didn't see anything mentioning server mods in etf2l rules but logically they would refuse
pugchamp is, i believe and mean no offense, in maintenance mode so changes may be harder to get in

https://twitter.com/Diabotical/status/1239372132913733632

https://www.thelocal.dk/20200311/denmark-to-shut-all-schools-and-universities-to-fight-virus
https://www.thelocal.dk/20200311/denmark-to-enter-new-phase-of-virus-battle-soon
Not looking good, sorry

I'm interested to know how the netcode works, playing in burger servers (~100/120ms) I had absolutely zero issue shooting, moving and rocket jumping.

It could mean that it's entirely client predicted (moving and rocket jumping isn't delayed) and heavily lag compensated (favor the shooter), the former is great, the latter is mostly fine until you get railed behind a corner or rocketed without seeing it being shot.

It's also possible they're blending in server-side extrapolation just like Reflex did, maybe with a different or no upper bound (Reflex has 80ms). If that's the case, then awesome.

https://clips.twitch.tv/DreamyLazyPorpoiseThisIsSparta

anyone wanna import that banlist in tftv?

Blue Snowball sounds OK but is bulky (read: shit to transport) and the cable connector is absolute garbage, absolutely requiring a homemade fix (I used Blu-Tack). It also gets you flagged at airport security for a free manual check.

An XLR setup should be attainable with 100EUR and will sound better than a lot of the USB mics available.

USB AT2020 also sounds quite good.

You're kinda comparing apples to oranges, YouTube views accumulate from when they are published, most of the TF2 player stats you're shown are fluctuating over a short span of time. I don't know of any website that keeps track of something similar for TF2 players, i.e.: how many unique players joined any server server since a point in time, the best you have is, I believe, how many people own the game on Steam, which is not very indicative.
The other thing is that YouTube is a lot more accessible than TF2, viewers may watch but not play at all.

https://youtu.be/ssr1PMSNvwk

I don't suggest self-hosting TF2 servers with the occasional DDOSer showing up every few months.
Also: NA Serveme added a bunch of premium servers when ESEA ended their TF2 league, as well as Gameye providing infrastructure that seems to be on par with what multiplayer AAA games have nowadays.

What does the timeline look like?
Isn't this going to hinder players who wanted to attend Copenhagen Games?

Are you running TF2 with an uncapped framerate?

I set up a mumble server on the NACL hosting for the time being, I believe it's in NYC:
ip: 68.183.50.247
port (default): 64738

q3's pretty much defined modern FPS netcode, source introduced some optimizations with no major changes
- packets are sent over UDP/IP, some redundancy and buffering is involved
- server sends diffs of the world state according to ack'd client state
- clients extrapolate their own state (movement/hitscan) and interpolate the state of the world
- backward reconciliation is used in case of misprediction

TF2 solely uses UDP for the gameplay netcode, TCP is used for RCON
I can't speak for Q2 but I highly doubt it uses TCP, it would otherwise be unplayable with ping and packet loss

There's some to remember:
Netcode can never be perfect online (until everyone gets hooked to fiber and a solution is found for routing I guess)
There'll always have to be downsides somewhere
Not every issue you see is caused by netcode, hitsound in TF2 requires a roundtrip because the client doesn't predict the damage caused

They are literally the same code