That's a good looking spreadsheet, how did you do data entry?

Cool tip: you can sort by column by clicking the Y shape in the tool bar, then Create New Temporary Filter.

Hey guys, thanks for bringing this up, I'll send this part of the thread to our server hosting contact, I highly suggest you take the five minutes it takes to report bad routing to Hiperz directly https://www.hiperz.com/knowledgebase/17/Reporting-high-ping-or-latency-issues.html
You should also keep in mind that the DDOS protection adds 5-15 ping to most players on average, but obviously it's not what's going on here.

Leaking from the cesspool that is the cathook users' chatroom:

- Time-based exploits are patched (instant decloak, instant cap)
- Weapon IDs changed (meaning some cheat features will be temporarily broken, in cathook's case, aimbot)
- Server crashing is still a thing
- Server lagging is probably still available through other commands (voicemenu 0 0 was used, this command could be replaced) EDIT: confirmed unpatched
- You can get matchmaking banned from in-game reporting
- They're attempting to use that to get innocents banned by mass-reporting everyone
- "tf2 is ded, no fun without instacap"

Please save yourself from spending so much money on a trip that will leave you extremely disappointed, no amount of talking will change how VALVe works, which is the fundamental issue as to why they can't keep up work on service-games, community weapons are neat but they're just fluff

You should be able to do a research for "Toggle Minmode" (do it case-insensitive) in the common menu files and find the element, it's not a standard one.

probably create a purist TF2 "clone" with middie bots and plug myself in until i rot away

https://clips.twitch.tv/CalmDeterminedMangoSquadGoals

ESEA will have 9 maps (8 current + 1 new)

Yeah! Just fix it! Right VALVe?

https://i.ytimg.com/vi/X60VLdrKsLQ/maxresdefault.jpg

Back to Community pubs I guess. o- o no. MyM happened.. :/

It's becoming incrementally harder to enjoy TF2, unplayable casual, performance issues, instability.
If it was up to me, I'd trade the last 3 years of updates with a semi-major update addressing major issues.

All in hudmatchstatus.res TeamStatus:
Does "chargeamount" and "ReadyBG"/"ReadyImage" actually work ?
Are there any other options to team1/2_grow_dir than "east" and "west" ?
Any way to y-offset the second team ?

Sneak peak https://i.imgur.com/vw0zuzl.jpg

Hey, just to make sure, the deadline is June 10th?
I'll give it a try, I have a few ideas.

If you suicide in spawn, you can instantly respawn by changing loadout or class
(I think this applies to fall damage deaths as well?)

File format is half-documented here: https://developer.valvesoftware.com/wiki/DEM_Format
I clearly recall Icewind (demos.tf creator) mentioning that he managed to slice demos into playable chunks, as for retrieving data, it can be done using https://github.com/demostf/demo.js or https://github.com/SizzlingStats/demboyz

What Brimstone said is true.
I do plan on providing additional stats, whether it be by generating logs for logs.tf or by proposing and coding features for demos.tf.
I can foresee that players would rather have all their logs in one website (that would currently be logs.tf) but the integration would be painful and error-prone.
I think demos.tf has more potential to be a more fitting service for us *and the rest of the community* in the long run:
- STV demos will never require a third party plugin to run (meaning ESEA demos could be uploaded)
- Additional features can be applied to older demos (whereas new logs features can't be backported)
- Intensive stats will never require the gaming server to choke
- Demos.tf software is open source, any kind of statistic can be added
- Hypothetical: stats could be generated directly from a live STV feed (granted you plug it before the match starts)
- 2d/3d Heatmaps
- Automatically slice demos for fragmovie makers

I could come up with even more ideas, the only limiting factor is my free time

There are some downsides, obviously:
- Demo analysis (without packet filter) can be quite CPU expensive
- Demos take more space
- Both meaning that stats may take longer to be available
- It's possible that STV demos are missing crucial packets to provide information to clone stats from logs.tf