A couple of years ago around (i61) I wrote a simple program to scan the logfiles for "fragmovie-worthy" events.
Since then I wanted to turn this program into a website at some point. So for the past year I've been working on it on and off.
So here it is: demoticks.tf
a simple way to find airshots, headshots etc. with the corresponding ticks in your tf2 matches.
There's currently two ways of getting events:
You can either search for any events done by any tf2 player or you can select .dem files that have a timestamp in them and the website will try to find the corresponding logs/events.
You can also if you used the latter create a .vdm file which should allow you to automatically record the events with lawena. I'm thinking about supporting other ways of automatically recording demo files e.g this so if there's any interest let me know!
To specify the player you can try enter his name and it should autocomplete it. If it doesn't it's not yet in the database and you need to specify the steam64 id first, after that all should be good.
I really hope you guys find it useful and if you have any suggestions let me know!
Notes
Show Content
- If your name isn't what you think it should be it's because I'm determining it in the following order: etf2l,ozfortress, logs.tf
Yes rgl isn't supported because their api can sometimes take forever to respond and it's currently also hosted on some temporary site.
- By adding a new dropdownlist to an event you specify that you want to look for both of them at the same time.
Adding a tab adds an independent event you also want to search for.
- Currently the search option only allows you to look at your last 1000 logs and you can only reqeust 200 at once. This is temporary since I expect the traffic to be quite high in the first couple of hours.
A couple of years ago around (i61) I wrote a simple program to scan the logfiles for "fragmovie-worthy" events.
Since then I wanted to turn this program into a website at some point. So for the past year I've been working on it on and off.
So here it is: [url=https://demoticks.tf]demoticks.tf[/url]
a simple way to find airshots, headshots etc. with the corresponding ticks in your tf2 matches.
There's currently two ways of getting events:
You can either [b]search[/b] for any events done by any tf2 player or you can [b]select[/b] .dem files that have a timestamp in them and the website will try to find the corresponding logs/events.
You can also if you used the latter create a .vdm file which should allow you to automatically record the events with lawena. I'm thinking about supporting other ways of automatically recording demo files e.g [url=https://github.com/juniorsgithub/tf2-renderdemo]this[/url] so if there's any interest let me know!
To specify the player you can try enter his name and it should autocomplete it. If it doesn't it's not yet in the database and you need to specify the steam64 id first, after that all should be good.
I really hope you guys find it useful and if you have any suggestions let me know!
Notes
[spoiler][list]
[*] If your name isn't what you think it should be it's because I'm determining it in the following order: etf2l,ozfortress, logs.tf
Yes rgl isn't supported because their api can sometimes take forever to respond and it's currently also hosted on some temporary site.
[*] By adding a new dropdownlist to an event you specify that you want to look for both of them at the same time.
Adding a tab adds an independent event you also want to search for.
[*] Currently the [b]search[/b] option only allows you to look at your last 1000 logs and you can only reqeust 200 at once. This is temporary since I expect the traffic to be quite high in the first couple of hours.
[/list][/spoiler]
fix the link, it drops you back to this thread lmao
fix the link, it drops you back to this thread lmao
pretty dope, not a fan of the colours though
pretty dope, not a fan of the colours though
BvYes rgl isn't supported because their api can sometimes take forever to respond and it's currently also hosted on some temporary site.
payload.tf currently hosts an API to gather player data.
read more about it here
The average response time is still ~5 seconds, however it's sometimes quicker than the rgl page itself.
Also is this on GitHub? If not, you should open source it!
[quote=Bv]
Yes rgl isn't supported because their api can sometimes take forever to respond and it's currently also hosted on some temporary site.
[/quote]
payload.tf currently hosts an API to gather player data.
[url=https://github.com/c43721/payload-neo/blob/master/src/api/README.md]read more about it here[/url]
The average response time is still ~5 seconds, however it's sometimes quicker than the rgl page itself.
Also is this on GitHub? If not, you should open source it!
Damn this is actually super cool, what exactly determines 'events', is it just like the cheat feed type stuff or logs airshots?
I have a bunch of old demos that I bookmarked after the fact but don't feel like looking back and finding the exact
timestamp, would it be possible to just see all the timestamps of your kills for example? (e.g., for medic u probably dont have many kills per match but one of them might be good and frag worthy despite not being a 3k or registering as an airshot on logs)
Damn this is actually super cool, what exactly determines 'events', is it just like the cheat feed type stuff or logs airshots?
I have a bunch of old demos that I bookmarked after the fact but don't feel like looking back and finding the exact
timestamp, would it be possible to just see all the timestamps of your kills for example? (e.g., for medic u probably dont have many kills per match but one of them might be good and frag worthy despite not being a 3k or registering as an airshot on logs)
really nice for fragmovies with the airshot, headshot and killstreak features
really nice for fragmovies with the airshot, headshot and killstreak features
bearodactylDamn this is actually super cool, what exactly determines 'events', is it just like the cheat feed type stuff or logs airshots?
I basically download the logfile from logs.tf and then go through every line. Currently I'm saving every mention of a headshot,airshot,medicDrop,capture,kill,backstab and medic death. Then I combine some of them into one event since e.g. a medic dropping and a person getting an airshot are two separate lines in the logfile. The killstreaks I "calculate" after the fact so that's why they don't match up with the ones from logs.tf sometimes but I tried to make it so it's as close as possible to the ones from logs.tf
For people who are interested how I define killstreaks:
Show Content
Basically if a kill happens it's a "killstreak" of 1. If in the next 10 seconds another one happens it's a killstreak of 2 etc. if there's a killstreak of at least 3 it gets added as an event.
bearodactyljust see all the timestamps of your kills for example
Maybe I'm misunderstanding you but if you want to just see every kill you made during a match you can just select "kill" as an event.
But based on your message I think it would be a good idea to add a filter so you can just look for the logs where you played as eg medic. I'll get around to doing that.
Oh but keep in mind that to simplify things I'm currently only saving the most played class. So if there was a log where you'd play 16 minutes of scout and 14 minutes of medic I'm currently saving it as you having played scout in that match.
Thanks for your input!
[quote=bearodactyl]Damn this is actually super cool, what exactly determines 'events', is it just like the cheat feed type stuff or logs airshots?[/quote]
I basically download the logfile from logs.tf and then go through every line. Currently I'm saving every mention of a headshot,airshot,medicDrop,capture,kill,backstab and medic death. Then I combine some of them into one event since e.g. a medic dropping and a person getting an airshot are two separate lines in the logfile. The killstreaks I "calculate" after the fact so that's why they don't match up with the ones from logs.tf sometimes but I tried to make it so it's as close as possible to the ones from logs.tf
For people who are interested how I define killstreaks:
[spoiler]
Basically if a kill happens it's a "killstreak" of 1. If in the next 10 seconds another one happens it's a killstreak of 2 etc. if there's a killstreak of at least 3 it gets added as an event.[/spoiler]
[quote=bearodactyl]just see all the timestamps of your kills for example[/quote]
Maybe I'm misunderstanding you but if you want to just see every kill you made during a match you can just select "kill" as an event.
But based on your message I think it would be a good idea to add a filter so you can just look for the logs where you played as eg medic. I'll get around to doing that.
Oh but keep in mind that to simplify things I'm currently only saving the most played class. So if there was a log where you'd play 16 minutes of scout and 14 minutes of medic I'm currently saving it as you having played scout in that match.
Thanks for your input!
hertzpretty dope, not a fan of the colours though
If enough people agree with you I might create an alternate/custom coloring scheme. Would be quite easy to implement although it wouldn't be my top priority.
[quote=hertz]pretty dope, not a fan of the colours though[/quote]
If enough people agree with you I might create an alternate/custom coloring scheme. Would be quite easy to implement although it wouldn't be my top priority.
24
But as far as I can tell it only supports RGL as well right?
I actually stopped doing player data requests synchronously some time ago I just completely forgot about it so I could just implement rgl again.
And about open sourcing it: While I do understand why, especially for this kind of project it is important to open source it, I'd like to work on it for a couple of months longer before I do so.
[quote=24][/quote]
But as far as I can tell it only supports RGL as well right?
I actually stopped doing player data requests synchronously some time ago I just completely forgot about it so I could just implement rgl again.
And about open sourcing it: While I do understand why, especially for this kind of project it is important to open source it, I'd like to work on it for a couple of months longer before I do so.
Bv But as far as I can tell it only supports RGL as well right?
I actually stopped doing player data requests synchronously some time ago I just completely forgot about it so I could just implement rgl again.
Yes, it only supports RGL, as ETF2l already has a robust API and there's no reason to make one myself.
Bv And about open sourcing it: While I do understand why, especially for this kind of project it is important to open source it, I'd like to work on it for a couple of months longer before I do so.
Understandable. Sometimes it's just not what you want to do.
[quote=Bv] But as far as I can tell it only supports RGL as well right?
I actually stopped doing player data requests synchronously some time ago I just completely forgot about it so I could just implement rgl again.[/quote]
Yes, it only supports RGL, as ETF2l already has a robust API and there's no reason to make one myself.
[quote=Bv] And about open sourcing it: While I do understand why, especially for this kind of project it is important to open source it, I'd like to work on it for a couple of months longer before I do so.[/quote]
Understandable. Sometimes it's just not what you want to do.