Please install the most recent version (version 0.1.6) and then try again. (The newest version now removes shots_hit and shots_fired, but only in such a proportion that the accuracy remains the same. Well you lose up to 1% to rounding errors per added log, but I think that should be fine considering it enables you to combine f.e. your 4 logs).

And to be honest, I am questioning myself why I didn't have the idea before which I now use to minify the log.
While trying to reduce the log I found methods to get the size down up till 11.2 MB, until I got the idea which is implemented now which doesn't use questionable tricks to slim the log size and still is almost sub 5 MB. (Although I still have the code, so there is potential for even smaller logs should the future need it).

Looking at your specific log I think there is some data which is removable which won't lose any stats, I will do a testing version of the log combiner and see if all your important stats stay and it is uploadable.

This seems to be quite the misleading error. I also tried to combine the logs you have and looking at the network and console output you can see the server responds with a 413 http status code, meaning

REQUEST ENTITY TOO LARGE

. The log you try to combine would be 15.16 MB big and that size is most likely above the upload limit. (It once was 5MB but I think it is bigger than that now, although I don't know the exact size). I will look into maybe a more clear error message (f.e. something like Log was too big to upload). I will also check again if there could be more done to minimize the log (I already know a way, but it is rather dirty and more like a hack and not good practice).

The latest version (0.1.5) should work correctly now, feel free to try it out. (You now have a settings menu when clicking the Jacks Log Combiner link on the bottom right).

To install just open the userscript page again on GitHub.

Good point, currently it removes that too to make the log smaller (shot_hit and shot_fired) - when I have time for it I will make an options menu where you can enter an API key and a toggle box for decreased log size (so by default accuracy will be kept intact)

[At least I assume they are used for that]

Hello,
there are already quite some log combiners around, but a friend pointed out to me, that there are no real quick online log combiners around anymore, and that the python log combiner I wrote is difficult to first time set up.

So I thought a bit about it and got to the conclusion that the simplest solution would be a userscript directly for logs.tf => Meaning I wrote one in the last 2 days (based on my python version).

You can see the result as a single image here:

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

or a quick video on how to use and install it here.

It is available on my github page.

Now you may ask why should you use it instead of alternatives? - So here a quick list of advantages:

• Installed as a userscript, meaning you are not dependent on a third party hoster but it is directly integrated into logs.tf (meaning you also don't need to copy URL's)
  
• You do not need to setup any installation/environment like Java or Python
  
• It automatically tries to fill in the map name for you (generated using the maps of the logs)
  
• It tries to reduce logs to the important parts (for log parsing) so the resulting combined file is smaller than other log combiners
  
• No need for an API key (although it requires the user to be logged in at least once with the script activated)

If you have any ideas / questions / suggestions feel free to tell me.

Changelog:

Currently it is only for 1 team, so players can set their availability (yes, maybe, no, unset) for every day (and 3 times every day) of the week and a team leader or deputy can add a scrim. So players can open the page and see the next scrims and team leaders know what the best time for a scrim is. If you are not in that team you are unable to see any of that data.

But I already thought about a system like that (and it is already written in Ideas for the Future on the About page). So people can not only create a already set scrim for a day but can create a "Looking for Scrim" entry (which can also have a time range), where they can select a region, a gamemode (HL, 6s, Prolander, ...) and a skill level. And then people can either filter for all LFS on a dedicated page or get a suggestion when creating their own LFS entry.

I have added RGL support now. But being new less testing was done than for ETF2L or UGC. So feel to report errors if you get some.
Example RGL Team Table (with me as simulated leader so I can test stuff): Short Video
Additionally errors could happen because I wasn't able to test edge cases because RGL is so new I didn't find a team which played multiple seasons (or do you have to make a new team for every season?).

If there is enough interest, I could imagine adding support for RGL teams