Forty-Bot
Account Details
SteamID64 76561198076693960
SteamID3 [U:1:116428232]
SteamID32 STEAM_0:0:58214116
Country United States
Signed Up January 23, 2020
Last Posted February 22, 2024 at 11:46 PM
Posts 29 (0 per day)
Game Settings
In-game Sensitivity
Windows Sensitivity
Raw Input  
DPI
 
Resolution
 
Refresh Rate
 
Hardware Peripherals
Mouse  
Keyboard  
Mousepad  
Headphones  
Monitor  
1 2
#24 trends.tf - TF2 stats collected from logs.tf in Projects

Feature update:

  • You can now view logs on the site. It is possible to combine up to five logs and view them just like an individual log. This should hopefully make manual log combiners mostly unnecessary.

    Some stats are not displayed. Medic stats like "average time before healing" are not displayed because it is impossible to display them accurately for multiple logs. In the future, I may display them as a list. Other stats like killstreaks and per-round stats are not currently extracted from the log summary information.
  • Replaced the trends chart library with C3.js (thanks Bv!). This should help with performance.
  • You can now vary the size of the rolling average on the trends page.
  • There are now links to RGL, UGC, ETF2L, and OZFortress on player profile pages.
posted about 2 years ago
#40 CALL OUT!!1! RGL YOUR TRANSPARENCY STILL SUCKS!! in TF2 General Discussion

I've come to make an announcement: Sigafoo the RGL admin's a bitch-ass motherfucker. He banned my fucking alt. That's right. He took his discord fuckin' moderator dick out and he banned my FUCKING alt, and he said his dick was THIS BIG, and I said that's disgusting. So I'm making a callout post on my TeamFortress.tv. Sigafoo the RGL admin, you got a small dick. It's the size of this second banana except WAY smaller. And guess what? Here's what my dong looks like. That's right, baby. Tall points, no quills, no pillows, look at that, it looks like two stickies and a rocket. He fucked my alt, so guess what, I'm gonna fuck TF2. That's right, this is what you get! My SUPER CROCKET PISS! Except I'm not gonna piss on TF2. I'm gonna go higher. I'm pissing on STEEEEEAM How do you like that, GABEN? I PISSED ON STEAM, YOU IDIOT! You have twenty-three hours before the piss DROPLETS hit the fucking game, now get out of my fucking sight before I piss on you too!

posted about 2 years ago
#23 trends.tf - TF2 stats collected from logs.tf in Projects

Feature update:

  • Avatars are now displayed on player profiles, search results, and on the leaderboard and peers pages. Player pages now use their name on steam.
  • I added a temporary site logo/favicon. I am still looking for someone to design a proper one.
  • The totals page now shows averages either per minute (for damage) or per 30m (for kills, etc.).
  • The weapons page now shows totals for kills, damage, logs, and time played.
  • There is now a discord which you can use to suggest features or report bugs.
posted about 2 years ago
#310 Logs.tf match stats in Projects

Some logs return 500 errors starting at https://logs.tf//3001608 and ending at https://logs.tf/3001646

I guess it could be a local-timezone as well if for some reason the server admin decides to make the logfiles non UTC

For a "fun" example of when this happens, see https://logs.tf/2726837

posted about 2 years ago
#22 trends.tf - TF2 stats collected from logs.tf in Projects

Feature update:

  • You can now sort the logs, peers, and weapons pages by (almost) every column. So e.g. you can find your highest DPM log, or the player you have the best winrate with.
  • There is now a leaderboard which ranks players by winrate with 50 wins/losses added (to help filter out players who have 100% winrate over 5 games). You can also sort by raw winrate, time played, and number of logs played. In addition, you can filter by class, map, and format, making it easy to answer questions like "Who's the best pyro player in Prolander on koth maps". Currently, leaderboard stats are recalculated every night.
  • And just for glass, I added the overview stats (winrate, W-L-T, etc.) to the totals page so you can filter by class.
posted about 2 years ago
#20 trends.tf - TF2 stats collected from logs.tf in Projects
ArieOne thing I would consider, is to move "log_wlt" and "player_last" from views to materialized views (unlike a view these need their own indexes). You could update these materialized views (concurrently) after a new batch of log files is imported. This might improve part of the peers query.

Hm, that's a good idea. Previously, player_last was a table, which I suppose is a kind of manually-materialized view.

supradoes this site has any sort of API?

Nope. Please send a PR :)

it would be cool to have it because then we could use it for skill prediction on tf2pickup.org I guess

This is being tracked by this issue. But it's not very high on the list of priorities atm. Though part of the reason for switching to postgres in the first place was so I could have multiple processes modifying the database at once, such as a process which calculated elo.

+ some option to filter 6v6/hl/2v2 games out from the rest when checking a player
that would be way cooler than looking at the divisions on etf2l for europeans, in case of burgers there is probably no good way to do that atm
no idea about apac

ps: this is probably the biggest issue why we don't have a european pickup site atm

I want to start scraping RGL at some point (see this issue). Unfortunately, RGL doesn't really have an API, so I'd have to scrape their site :l. Honestly, if ETF2L has an API I would look into them first.

glasscouple things i noticed

-tried filtering blaze's logs down to just soldier on product in the logs.tf era, and it returned nothing

Can you link? Thanks.

-is there a way to generate winrate after filtering out ultiduo and stuff?

Nope, sorry. I'm working on adding filters for every page on the site, but the overview hasn't gotten that treatment yet. Though perhaps I could just add this to the totals page...

-b4nny has 283% acc on pyroTimTumthe pyro acc is possible because of the detonator or other flare guns

Basically this. At the moment there is not too much processing on top of raw stats from logs.tf. So if/when I write my own logs parser we can address this. But until then pyro will always have like 3x the hits vs shots.

-class stats seem inaccurate. it is claiming arrek is undefeated on sniper, n=5. is that like, logs where he played majority sniper

Winrate is calculated based on games with at least ⅔ time on this class. You can hover over the column headers and the tooltip will show some of the criteria. DPM, accuracy, and time played are based on all times you played that class.

cheers. don't change the design. every website built after 2010 looks like shit

I didn't have much of a choice :)

(that being said, if anyone can help me make a logo/favicon or can help with the CSS, I'd appreciate it)

posted about 2 years ago
#15 trends.tf - TF2 stats collected from logs.tf in Projects

Ok, I've addressed most of the major performance issues. The responsiveness should be back to what it was before the migration. I'm still importing logs from the past week, but it is going much faster than it had been.

ArieI'll take a look if you share some slow queries (use postgres' slow query logger) and the entire DDL (pg_dump --schema-only) and put it in a github gist.

Here's the explain analyze output for the peers query, which is currently the slowest page on the site. And here is the schema. My current plan is to move most columns out of the round table to reduce the amount of data we have to read in that inner loop to determine win/loss statistics.

posted about 2 years ago
#13 trends.tf - TF2 stats collected from logs.tf in Projects

A little update:

I'm migrating the database from SQLite to PostgreSQL. I started this last week, and did the switchover this past weekend. However, some of the queries are now taking way longer than they used to. I am currently working on this. Availability might be a bit spotty until I can get to the bottom of things. I am also trying to get log importing back up, but that is going much slower than before too. Please be patient for the next few days :)

In the longer term, performance was and is a big problem with the site, even before switching databases. I would love if some more experienced developers could look over my schema/queries and help out.

posted about 2 years ago
#9 trends.tf - TF2 stats collected from logs.tf in Projects
janga7would be sick if you could filter certain logs. shit like filtering out ultiduo logs

Good idea. I made an issue for it.

edit: Seemed really simple, so I just added it. Have fun ;)

posted about 3 years ago
#7 trends.tf - TF2 stats collected from logs.tf in Projects
MitchThese stats are really good. What I'd love to see now is if you could make a rankings leaderboard out of all the data you've made.

Yeah, I'd like to add some kind of elo eventually. But there are a lot of other things which need doing first.

posted about 3 years ago
#4 trends.tf - TF2 stats collected from logs.tf in Projects
24Looks straight out of 2010, but the details and the data are phenominal. Great job on this!

Thanks! Any web design help would be great, since it's not really my area of expertise.

24You may be intriuged to port into DigitalOcean and their App platform. The CI/CD as well as horizontal/vertical scalability is amazing for these types of projects - you just won't be able to run a local SQL DB in this environment, but you could just run a Droplet for an additional $5 or an AWS instance for free (for up to 12 months) or GCP (for up to 12 months) I have some credit I can send your way if you wish to experiment with this.

I looked into it a while back, but I had $100 of credit on Azure, so I decided to use them (at least initially).

posted about 3 years ago
#1 trends.tf - TF2 stats collected from logs.tf in Projects

trends.tf

All the useless stats you've ever wanted.

Currently running on the cheapest Azure instance I could find, so try not to hug it too hard. Initial page loads can be pretty slow (5-10s), but everything after that should be faster.

Around 2ish years of logs are imported. I eventually plan for everything to get imported, but for the moment I am only importing new logs.

This website is open source, so please feel free to open an issue or pull request. I will try to fix bugs, but I have a pretty big feature backlog already. If you would like to see a new feature, you can react to the issue and that will help me decide what to work on. At the moment I am trying to get the database ported to PostgreSQL so I can have multiple inserts running at once :)

posted about 3 years ago
#305 Logs.tf match stats in Projects
I'm not 100% certain but 90% certain that if you were to update a log e.g on a per round basis it keeps the same logid.

Does the upload time get updated? And is there a limit to when a log can get updated? E.g. could I update a log I uploaded 1 year ago?

If I take a look at the log you mentioned in which Kumis has 38634(heal) for some reason almost every shot he makes as a scout looks like this

This is actually super common. A significant amount of his logs have over 500 heals/minute, even though he never plays medic (or even engie). You can look at any other player and see the same effect.

posted about 3 years ago
#301 Logs.tf match stats in Projects

Can you add the ability to paginate starting at a specific logid? E.g. something like

https://logs.tf/api/v1/log?before=some_logid

. A naïve iteration will get duplicate logs. E.g. imagine if there are 25 logs and I have a limit of 10. The first request will get logs 24-15. Then someone uploads a new log. I then ask for another 10 logs, starting at offset 10. This gets me logs 6-15. Notice how log 15 gets requested twice. If the import lasts for a long time (and no corrective measures are taken), this can end up being a significant fraction of the requested logs.

I would also like to verify a few things about the JSON. Is info.date the upload time? In UTC? And rounds[].start_time in the local timezone? Do new log uploads get their own logid even if they are updates to another logid? Or do they keep the same logid as the log they update? Does info.date change if the log is updated? Is there a "statute of limitations" after which a log can no longer be updated?

And lastly, what in the world does players[].heal represent? On some logs it seems to represent healing done, and on others it seems to count self-healing. For example in this log, Kumis has 38634 heal and in this log he has 0, even though he played scout/heavy both times. Complicating matters, for medics the player[].heal mostly equals the sum of healspread[][], which implies that it is healing done.

posted about 3 years ago
1 2