This userscript logs matches to an awesome and unforeseen level of detail, yielding great opportunities for analysing individual matches, maps, players and the game in general. These opportunities extend way beyond how matches are currently visualised on this website. The raw data of all matches is openly available for everyone to analyse and research as they wish.
While tagpro.me collected a great set of data, it only logged match totals rather than detailed timelines of matches. The data collected by this new userscript has much more potential for gameplay research.
For completeness sake, we nevertheless integrated the old data into our new database. These old matches are included in all search functionality of this website and have a match id starting with
The old tagpro.me database recorded games from 13 July 2014 until 6 April 2015. The TagPro Analytics database commenced recording shortly thereafter on 25 May 2015 and is still recording while you read this.
Yes, including Capture-the-Flag, Neutral-Flag, Potato, Marsball and combinations thereof. For maps with multiple flag types, the type of flag is even indicated for all events and statistics. Note that for marsball matches, button time includes marsball push times, and unlike in the game itself, marsball returns are also counted as tags for simplicity of the logging system. The system could even be used to analyse Racing games or Open-Field-Master games. Note that even Top Speed power-ups are fully supported!
You can use it as both. The userscript has been carefully designed to only collect data that both spectators and all players receive from the game server. You only need to make sure that you join the game before it starts and don’t quit before it ends.
Always check the rules of the specific league to be sure. MLTP allows stat-collecting scripts in general. ELTP explicitly approves and even requires TagPro Analytics.
The userscript has been restricted to data that both spectators and all players of a match can receive. You can read more about the userscript design considerations on /r/tagprostatistics. If you are a spectator and really want to collect all possible data like an NSA, you should perhaps look into a userscript like TagPro Replays, although for large-scale analyses this means you also need to upgrade your storage capacity like an NSA.
The detailed logging indeed allows for some new aggregate statistics to be defined. These are indicated below.
It indicates a flag that is grabbed and then captured or dropped within the same time step. The former for example occurs when in Neutral-Flag games you tag an enemy flag carrier within your end zone.
On a map, it simply represents a generic power-up. On scoreboards and in timelines it indicates someone collected a duplicate power-up, i.e. another instance of a power-up that was already active for that player.
The support statistic has been split into a block statistic and a button statistic, which are considerably more meaningful.
Unfortunately, prevent can only be detected at 1-second intervals and block and button can only be detected at 5-second intervals.
This depends on the server, due to technical differences between test and production servers. The Koalabeast maptest server uses an old version of TagPro resulting in all power-up data being omitted. On the NewCompte servers, we can only accurately record the number of power-ups, but in general not their type or duration, because this information is restricted to sight distance.
All dates and times displayed are in Coordinated Universal Time (UTC) and in 24-hour format. The current time in UTC is 15:58 (3:58 PM) on Tuesday.
If the match is important to you, you can always save the match file on your computer. Such a file can be visualised later on this website. If you did not save the file right after the match, you can still save it by visiting the homepage of this website in the browser you play TagPro with. From there you can still access your last ten matches and visualise or save them as needed, even if the website was offline when the matches were played.
Otherwise, just check the error message to find out whether you need to do something, and if so, what. Sometimes the error message may ask you to update the userscript, e.g. if a bug is found in the data collection code.
TagPro Analytics records the team names as they were set in the group settings. To set custom team names, the group leader must click on a team name on the group page and type a new name in its place.
The win rate shown is based on the flairs you used. To fix your profile, simply record one game in which you play with your highest flair.
Development of this userscript began before TagPro Next was announced. Despite the commitment of Koalabeast to support modding, it is way too early to tell if/how something similar to this is possible.
Each match in the database can be downloaded as a data file, as if you spectated the match yourself. The download link is located at the bottom of the scoreboard. It contains JSON with the most important fields containing base64-encoded binary data. Instructions for reading the file format are provided on the Science page. That page also contains instructions on how to download the database of this website in bulk for multi-match analyses (old tagpro.me records are only available in bulk).
Yes, all TagPro Analytics users unite at /r/tagprostatistics for everything related to TagPro Analytics and other methods of statistical analyses of TagPro matches. Of course you can also find some of the stuff on the main /r/tagpro, but the statistics subreddit discusses all the details and is easier to browse due to the low volume of posts.
Yes, this website crawls threads on selected TagPro-related subreddits linking to it, adding those threads to the threads list and linking them to the specific matches mentioned in the thread. The crawler discovers a new thread once someone clicks from the Reddit thread to this website. Previously crawled threads are periodically checked for updates. Contact me if I missed a relevant subreddit.