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.

Does self damage count towards dtm?

If you shoot yourself in a tf2 match it doesn't get added to the log file. Therefor it won't be added towards damage taken or damage dealt.
If you look at the code zoob uploaded some time ago for is 1.0 version of the log parser (which isn't the version currently being used for sure) the only thing that increases damage dealt/taken is the event : ' triggered "damage" '. So if you were to configure a server to log the events when you shoot yourself as "(player 1) triggered "damage" against (player 1)". It would be taken into account.

info.date is the upload time in UTC.
rounds[].start_time originates from the log file. It's basically the time next to the logfile event: " L 12/27/2020 - 20:38:19: World triggered "Round_Start" "
There's some other keywords as well but it's one of them. I'm pretty certain logs.tf assumes the logfile is in UTC therefor the time you see is also in UTC. I guess it could be a local-timezone as well if for some reason the server admin decides to make the logfiles non UTC.
This also means that the rounds[].start_time could be days before info.date as well btw.

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.

I will look into the players[].heal tomorrow a bit more but I believe it should be the healing the person has issued e.g the amount of healing a medic has done.
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

L 12/27/2020 - 20:39:03: "Kumis<14><[U:1:169048576]><Red>" triggered "damage" against "Dummy<11><[U:1:389475398]><Blue>" (damage "3") (weapon "scattergun") (healing "82")

I don't know what happened there but that's most likely the root cause of why he has such a high healing stat.

Hope this helps a little bit!

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?

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.

Can someone explain how is this possible?
Looks like this https://logs.tf/2932021 is a changed version of this https://logs.tf/2931449. Not only names and some stats have been changed, but also killstreaks and chat messages.

Would anyone know how accuracy is calculated for the logs? The info itself is not in the JSON files that logs.tf provides, so I'm assuming its calculated from the raw logs, but I have no idea how its calculated exactly.

Any help?

discovered it literally after this post, its just shots hit in the json divided by total shots

Looks like someone did a find & replace for some name + steamids, as well as scores, and the chat:

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

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

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

I'm not sure if it's just an idea but, is it possible to make the uploaded logs unlisted? I own a linux dedicated server that I use from scrims and I want to save the logs for my team.

It's just an idea- there's no such feature nor is there probably hope of this feature coming to life anytime soon.

I offer a plugin with Payload to automatically render log previews when a game is detected as "finished"; you can see that plugin here: https://www.teamfortress.tv/59986/payload-logs-plugin which may help you somewhat.

I'm not surprised. From what I heard, tf2 logs are fist being locally saved in your server directory and then uploaded to logs.tf, right? Is the log file like in the root 'tf' folder or where should I find it?

In

tf/logs

tf/logs

I might be blind but the only type of log files I'm seeing in there are typical raw console logs. Nothing else in particular to resemble the logs.tf type of logs.

they are indeed the same logs; logs.tf simply parses all of the raw data into something more digestible/readable for the average player and uses server plugins like F2's Medic Stats and SupStats2 to add additional data that would be otherwise missing

Would it be possible to make it so that it shows you the tick at which you had "biggest Uber Advantage Lost" so that one can look back to see why they miss counted Uber or why they didn't use their AD.

.

what is 9/0 friend

High level of 500s and 504s, something's dead I assume. :(

https://logs.tf/api/v1/log has been dead since yesterday

ninja edit: main page down now too :L

it's not dead, i can open it now but the problem in general is that the site lags in some random moments where if the logs.tf reaches a certain amount of time, it hits the timeout and the logs are not sent

i bet i'm not the first person asking for this, but if zoob is unwilling to devlop the code of the logs.tf, maybe he could make the source code open and let people who actually care about this game do something with it?

i bet his ad revenue is neat but the site is laggy and there are things to improve such us stuff mentioned in this thread or for example adding heals from crossbow to the general medic heal stats

Hey, idk if there is somewhere better to mention this or if you've already been notified, but some loser is uploading a bunch of doctored logs with slurs n nonsense.

https://logs.tf/3176253#76561198002105259
https://logs.tf/3176251#76561198002105259

Banned from trends.tf. Nothing I can do about logs.tf.

And just to answer my own question, the upload time gets updated any time the log is modified. Logs can be updated at any time.

It’s Cheeto

I've heard that it's him but I figure using his name is just giving him the attention he so desperately wants.

https://logs.tf/3176316#76561198079513105

how do i get this log deleted its just sitting in my logs now and one of the freaks edited it

Probably wait for a response by zooob to remove all these fake logs.

Unlikely to happen IMO...

Seems like there's a trend now where you download the log, modify it to say bad words towards a player and use a spare steam account to upload it.
https://logs.tf/3180356#76561198063542912