So for some reason in log files certain medigun names are listed as "unknown". Could be a logs.tf API bug, might happen whenever someone is using a modified medigun (re-skin, australium, festive, etc.). Every medigun in your log files was named "unknown" so there was no way of differentiating between uber and kritz. The bug has been fixed now, but unfortunately uber and kritz charges have been merged into one number.

Download link updated.

What filtering settings did you use?

Python script that iterates through up to 10,000 logs on a player's account and calculates every stat imaginable. It can output many different things depending on what you want to search for, such as average dpm, total caps, total time played on a class, etc. It's fully customizable, offering a wide range of search terms and various log type separation.

This is the third version of a script that I first started working on about 6 months ago. I returned to developing it yesterday because of boredom and dissatisfaction with the slow log grabbing speed. Version 3 now has multithreading, so calculation times have been sped up considerably.

Features:

• Date Range Filtering
  
• Gamemode Separation
  
• Class Separation

For Specified Classes:
Total Kills
Total Deaths
Total Damage

Average Kills per 30m
Average Deaths per 30m

Total DPM
Total K/D
Total Time Played

Also Includes:

• Medic Stats (Healing, Charges, Drops)
  
• Total Caps
  
• Combined version of specified class's stats

Unfortunately, Logs.tf rate limits their website when accessed from one point too frequently in a short period of time. The "Cooling Down (Logs.tf Data Request Overflow)" that you see every 20-25 logs is the result of logs.tf denying access to more pages, each time the script receives this error it stops all threads for 2.25s. On my PC I average between 9 - 13 logs per second. I ran it on a virtual machine and was averaging 5 - 7, the speed at which the iterator runs is completely dependent on your internet speed and CPU.

The Logs.tf API only supports logs that use the latest uploader plugin. All logs pre 2013 or servers you've played on
with the old plugin will be detected as broken and won't be calculated towards your final stats.

Download

Source Code

confirmed NOOB KILLER will own you in MGE on his laptop

Feel free to keep posting suggestions everybody, I'd love to expand on this project more.

Turns out the script was using the search term "heavy" instead of "heavyweapons". Should be fixed now, download link has been updated.

I'm definitely considering making it open source, if enough people ask for it then I'll probably post it. Utilizing multithreading in this project is actually kind of a beast idea, I'll give it a go soon.

Edit: Decided to just say fuck it and post SC. Enjoy!

Throughout the last four days I've been working on a python script that searches through all of an inputted steamID's logs.tf pages. It can output many different things depending on what you want to search for, such as average dpm, total caps, total time played on a class, etc.
It's fully customizable, offering a wide range of search terms and various log type separation. This is the second version of an older script that was posted about a week back, here are all the new additions and changes:

Features:

• Date Range Filtering
  
• Gamemode Separation
  
• Class Separation

For Specified Classes:
Total Kills
Total Deaths
Total Damage

Average Kills per 30m
Average Deaths per 30m

Total DPM
Total K/D
Total Time Played

Also Includes:

• Total Caps
  
• Combined version of specified class's stats
  
• Intuitive UI

This is my first large-scale python project, so you're gonna have to live with the occasional error / crash / miscalculation. If you run into a bug and you're willing to report it, please let me know the inputs you gave leading up to it and I'll try to fix whatever went wrong in the code. I'll update the download link for every patch that's made.

If you have a logs.tf profile with over 10,000 logs, it'll only include the first 10,000 logs. This is due to the maximum amount of logs that logs.tf can show on the json version of a player profile. However, the script will now skip 'broken / old logs', so logs from before 2013 won't be included anyway. I tested it on b4nny's account and let it run while I went out to eat. His 9,700 logs look just under 2 hours to iterate through.

Download

Source Code

To do:
Utilize multithreading to speed up search times
Airshot calculator
Heal stats calculator

Must've been an error while iterating through a specific log. Most of these issues will be fixed when I upload v2 of the program in a couple days.

Very cool stuff, I've only been using python for about a year so I'm always looking forward to learning more. I'll definitely take a look at these and see what I can use in my project.

Thanks for introducing me to this, search times will be significantly sped up using this method.

Edit: After testing out this method a little bit I've noticed a couple things. The API / json version of log files are grabbed nearly just as fast as the original page source code. This is due to the limited internet speed of the python requests module, which can access most websites like logs.tf/<log-id>; just as fast as it's API counterpart. I'll definitely still be using the API / json method for grabbing log files purely because it's much easier to read and iterate through, however don't expect a major speed increase. The API for the profile page seems very handy, as it completely eliminates the "Preparing for Iteration" you see when you first run the script by quickly grabbing the entire list of a user's log IDs. It'll also be a big help when I start developing custom searches, as it shows the date and how many players participated.

This started as a small project but I can see a lot of people are enjoying it! Thanks for the feedback everyone, I'm taking all of your ideas into consideration and will be expanding upon this project soon :)

Change name from Exboxs to mimky

Last night I started writing a python script that would iterate through all logs.tf files linked to an inputted steam ID. It grabs all the important details from your logs and averages them out to give you a good idea of your logs.tf profile as a whole. It runs in a CMD window and has been compiled to .exe using PyInstaller.

Features:
Average DPM
Average KD Ratio

Average Kills/Game
Average Deaths/Game

It only runs at the speed of which the requests module in python can harvest a logs.tf page source code. I've found that it takes on average 0.795s to iterate through an entire log file and isolate a specific steam ID's elements. The Average KD ratio grabbed from logs.tf will be slightly different than dividing Average Kills by Average Deaths due to rounding error.

Download

Source Code

Version 2 is now available here: https://www.teamfortress.tv/57870/python-logs-tf-stats-calculator-v2