Yes, but I'm not a fan of how it's mandatory js and how it randomly breaks every so often.
At the moment the server load is basically fine again. I'll burn those bridges when I have to.
| Account Details | |
|---|---|
| SteamID64 | 76561198076693960 |
| SteamID3 | [U:1:116428232] |
| SteamID32 | STEAM_0:0:58214116 |
| Country | United States |
| Signed Up | January 23, 2020 |
| Last Posted | October 6, 2025 at 12:02 AM |
| Posts | 34 (0 per day) |
| Game Settings | |
|---|---|
| In-game Sensitivity | |
| Windows Sensitivity | |
| Raw Input | |
DPI |
|
Resolution |
|
Refresh Rate |
|
| Hardware Peripherals | |
|---|---|
| Mouse | |
| Keyboard | |
| Mousepad | |
| Headphones | |
| Monitor | |
Yes, but I'm not a fan of how it's mandatory js and how it randomly breaks every so often.
At the moment the server load is basically fine again. I'll burn those bridges when I have to.
ArieForty-BotI expect I'll have to do something like this again sooner or later.
The slop bots demand more data. Have you considered putting slower pages behind a steam login, or the whole site perhaps?
Yeah. But I think it's better if there are fewer restrictions on browsing. There's less friction when people share pages. I'll probably have to do it eventually, but I'd like to put it off as long as possible.
There has been a steady increase of (AI) bots crawling the site. Last summer I added IP-based rate-limiting and blocked some user agents, which helped. But now bots will use unique IPs and browser user agents. In July I implemented some performance improvements to the log page, since bots really like to combine logs and then remove logs from the combined log. That helped a but, but the bots actually started crawling even more aggressively as a result.
So at the beginning of September I started blocking all bots that pretend to be Chrome older than version 100 or pretend to be Chrome but don't send the Sec-CH-UA header. That cut traffic by around 10x:
https://i.imgur.com/OKQ3zEl.png
I expect I'll have to do something like this again sooner or later.
RahmedThere seems to be an error
Hey man, no shame in success :)
Two new shinies since last time:
Small update: RGL matches are now also tracked. They haven't really fixed their API (and there are a lot of data issues in older seasons), but it's good enough now to use. I'm still working on improving the UI, especially regarding roster dates.
Regarding OZF, I have no plans to implement support atm. When linking logs to matches, I look for logs within 12 hours of the scheduled match time with enough players from both teams. However, OZF doesn't store the scheduled match time anywhere. All they have is the last time the match page was updated, which includes comments from way after the match.
No plans for UGC, CEVO, etc. since I don't have anything from before 2019 imported at the moment. Maybe in the future.
WiethoofdForty-Botautomatically combine all logs in a matchKinda neat feature, does this have some API output if the parsing is better than logs.tf? (properly combining team scores on stopwatch maps for instance isn't flawless: 6-0 score when team names are known in the 2-1 series)
The scores are combined properly. The scores in ETF2L don't necessarily match the round scores. As I understand it, there are always 6 points to be won. So if you win a map you get 6 points.
Also noticed a thing with testing the combining, and noticed that because of the serveme + pickup site duplicate uploads your detection for that at least works, but then still combines them in the output, e.g. this.
If you explicitly request to combine two logs, they will be combined. No matter if one is marked as a duplicate or not.
(and in case when combined, chronologically order them?)
Combined logs are ordered in the order you check the boxes (I think).
Logs might now also support pause duration in the output, is this parsed yet and taken into account for DPM calculations?
Pauses should be accounted for when calculating durations. That said, I don't re-parse logs (yet) so the stats are all the same as on logs.tf.
Also ozfortress should have an API, could link their matches and logs too!
Yeah, I'm interested in doing ozfortress as well. I couldn't find their API, if it exists.
This one's been a long time coming, but logs are now linked to ETF2L matches. That means you can go to your team and see all your matches and their associated logs, automatically combine all logs in a match, filter your logs by whether they were part of a match, and see which players had the best DPM this season (or all time).
I'm pretty happy with how this turned out. 97% of matches are linked automatically, but I will be continuing to improve this over the coming months.
I did ETF2L first because they have a proper API. RGL has been working on theirs, but they are still lacking in some major areas. I hope to add RGL support soon, once they iron out their issues.
Long time no update. I's been over two years since I started this website, and almost a year since the last update, so I figure a post is long overdue. I've been doing mostly incremental changes over the past year. Similar to last time, a lot of stuff is on the backend
In addition, there have also been some feature updates
Once again, please send me any bugs or suggestions you have either on Discord, Steam, or as a reply in this thread.
This map is way too big for 6s. Maybe it's good for pubs (12v12).
OK, here's my collected list of grievancessuggestions for DM. I think DM is like 70% of being perfect. I don't know how difficult these are to implement from a technical PoV. Disclaimer: I play open scout.
Please let me know how I can help out and make some of these happen. I really appreciate the DM servers; I think they've helped me become a lot less bad.
ArieProbably wait for a response by zooob to remove all these fake logs.
Unlikely to happen IMO...
Can you add a license? I'd love to have a look at this.
edit: Thanks!