The various tags can be separated into types:

• Application settings
• Output URL links
• HTML code blocks
• Statistics

HTML Tag	Category	Template Used in	Purpose	Dependencies	Notes
SETTING_PLAYER_SORT_NAME_TEMPLATE_FILE	Output URL links	All	Used for URL linkage to player listing sorted by name	None	Use this when you want your output to have URL links to the exact name of another template. For example: <a href="<!--SETTING_PLAYER_SORT_NAME_TEMPLATE_FILE-->">Sort Players by Name</a>
SETTING_PLAYER_SORT_KILLS_TEMPLATE_FILE	Output URL links	All	Used for URL linkage to player listing sorted by kills	None	Same as above
SETTING_PLAYER_SORT_DEATHS_TEMPLATE_FILE	Output URL links	All	Used for URL linkage to player listing sorted by deaths	None	Same as above
SETTING_PLAYER_SORT_RATIO_TEMPLATE_FILE	Output URL links	All	Used for URL linkage to player listing sorted by K:D ratio	None	Same as above
SETTING_PLAYER_SORT_ROUND_RATIO_TEMPLATE_FILE	Output URL links	All	Used for URL linkage to player listing sorted by best round (K:D ratio)	None	Same as above
SETTING_PLAYER_SORT_ROUND_KILLS_TEMPLATE_FILE	Output URL links	All	Used for URL linkage to player listing sorted by best round (num kills)	None	Same as above
SETTING_PLAYER_SORT_ROUND_KILLS_TEMPLATE_FILE	Output URL links	All	Used for URL linkage to player listing sorted by best round (num kills)	None	Same as above
SETTING_PLAYER_SORT_KILL_STREAK_TEMPLATE_FILE	Output URL links	All	Used for URL linkage to player listing sorted by kill streak	None	Same as above
SETTING_PLAYER_SORT_DEATH_STREAK_TEMPLATE_FILE	Output URL links	All	Used for URL linkage to player listing sorted by death streak	None	Same as above
SETTING_PLAYER_SORT_MINUTES_TEMPLATE_FILE	Output URL links	All	Used for URL linkage to player listing sorted by minutes	None	Same as above
SETTING_PLAYER_SORT_KILLS_MINUTE_TEMPLATE_FILE	Output URL links	All	Used for URL linkage to player listing sorted by kills per minute	None	Same as above
SETTING_PLAYER_SORT_DEATHS_MINUTE_TEMPLATE_FILE	Output URL links	All	Used for URL linkage to player listing sorted by deaths per minute	None	Same as above
SETTING_PLAYER_LIST_MAXIMUM	Application settings	All	Reports the maximum number of players that will be listed by the application	None	Use this when you want to show how many players can be listed in the player listings, like "Top 10" or such.

HTML Tag	Category	Template Used in	Purpose	Dependencies	Notes
PLAYER_NAME	Statistics	All	Player's name inserted here	None	Applies to individual stat pages and player listings.
STAT_KILL_STREAK	Statistics	All	Longest kill streak a player has	None	Same as above
STAT_KILL_STREAK_MODIFIED	Statistics	Individual stat pages	Modified kill streak value	Applies only to average stat generation	This stat is filled in when average stats are generated. The app takes the value of the player's longest kill streak, compares it with the average kill streak, and comes up with two numbers for insertion into the HTML output. The largest integer that can be returned is based on the application setting Stat Modifier Maximum. These numbers are whole integers, so you can use them as width tags to images or tables to create bar graphs that accurately reflect a player's score as compared to the average. See also AVERAGE_STAT_KILL_STREAK_MODIFIED and the application setting Stat Modifier Maximum.
AVERAGE_STAT_KILL_STREAK	Statistics	Individual stat pages	Longest kill streak an average player has	Applies only to average stat generation	Applies to individual stat pages only
AVERAGE_STAT_KILL_STREAK_MODIFIED	Statistics	Individual stat pages	Modified kill streak value for average player	Applies only to average stat generation	This stat is filled in when average stats are generated. The app takes the value of an average player's longest kill streak, compares it with the player's kill streak, and comes up with two numbers for insertion into the HTML output. The largest integer that can be returned is based on the application setting Stat Modifier Maximum. These numbers are whole integers, so you can use them as width tags to images or tables to create bar graphs that accurately reflect a player's score as compared to the average. See also STAT_KILL_STREAK_MODIFIED and the application setting Stat Modifier Maximum.
STAT_KILL_STREAK_DATE_TIME	Statistics	All	Date the player achieved the kill streak	None	Applies to individual stat pages and player listings.
STAT_KILL_STREAK_MAP_NAME	Statistics	All	Map the player achieved the kill streak on	None	Note that kill and death streaks can overlap into the next map. IE if a player kills 10 people without dying on one map, then proceeds to kill another 10 on the next map before dying, their kill streak would be 20. Stat is reset on any disconnect. Applies to individual stat pages and player listings.
STAT_DEATH_STREAK	Statistics	All	Longest death streak a player has	None	Applies to individual stat pages and player listings.
STAT_DEATH_STREAK_MODIFIED	Statistics	Individual stat pages	Modified death streak value	Applies only to average stat generation	See STAT_KILL_STREAK_MODIFIED for a desciption of what these modified tags are for.
AVERAGE_STAT_DEATH_STREAK	Statistics	Individual stat pages	Longest death streak an average player has	Applies only to average stat generation	Applies to individual stat pages only.
AVERAGE_STAT_DEATH_STREAK_MODIFIED	Statistics	Individual stat pages	Modified average death streak value	Applies only to average stat generation	See STAT_KILL_STREAK_MODIFIED for a desciption of what these modified tags are for.
STAT_DEATH_STREAK_DATE_TIME	Statistics	All	Date the player suffered through the death streak	None	Same as above
STAT_DEATH_STREAK_MAP_NAME	Statistics	All	Map the player suffered the kill streak on	None	Same as above
STAT_BEST_ROUND_RATIO	Statistics	All	Best round (K:D ratio) a player had	None	Same as above
STAT_BEST_ROUND_RATIO_MODIFIED	Statistics	Individual stat pages	Modified best round ratio	Applies only to average stat generation	See STAT_KILL_STREAK_MODIFIED for a desciption of what these modified tags are for.
STAT_BEST_ROUND_RATIO_KILLS	Statistics	All	Number of kills the player had in achieving the best round K:D ratio	None	Same as above
STAT_BEST_ROUND_RATIO_DEATHS	Statistics	All	Number of deaths the player had in achieving the best round K:D ratio	None	Same as above
AVERAGE_STAT_BEST_ROUND_RATIO	Statistics	Individual stat pages	Best round (K:D ratio) an average player scored	Applies only to average stat generation	Applies to individual stat pages only.
AVERAGE_STAT_BEST_ROUND_RATIO_MODIFIED	Statistics	Individual stat pages	Modified best round ratio	Applies only to average stat generation	See STAT_KILL_STREAK_MODIFIED for a desciption of what these modified tags are for.
AVERAGE_STAT_BEST_ROUND_RATIO_KILLS	Statistics	Individual stat pages	Number of kills in best round (K:D ratio) an average player scored	Applies only to average stat generation	Applies to individual stat pages only. I left this tag off the sample pages, as the value obtained here does not directly correlate to the overall average K:D ratio for the stat. For example, the ratios 5:1, 16:4, and 24:8 are 5.0, 4.0, and 3.0. That averages to a K:D of 4.0 for those three players. The average number of kills is 15, and the average number of deaths is 4.3333. Calculating the average K:D for those values, however, equates to 3.462. The tag is supported, however, if you wish to display it.
AVERAGE_STAT_BEST_ROUND_RATIO_DEATHS	Statistics	Individual stat pages	Number of deaths in best round (K:D ratio) an average player scored	Applies only to average stat generation	Applies to individual stat pages only. I left this tag off the sample pages, as the value obtained here does not directly correlate to the overall average K:D ratio for the stat. For example, the ratios 5:1, 16:4, and 24:8 are 5.0, 4.0, and 3.0. That averages to a K:D of 4.0 for those three players. The average number of kills is 15, and the average number of deaths is 4.3333. Calculating the average K:D for those values, however, equates to 3.462. The tag is supported, however, if you wish to display it.
STAT_BEST_ROUND_RATIO_DATE_TIME	Statistics	All	Date the player achieved the best round on	None	Same as above
STAT_BEST_ROUND_RATIO_MAP_NAME	Statistics	All	Map the player achieved the best round on	None	Same as above
SETTING_BEST_ROUND_RATIO_MINIMUM	Application settings	All	Minimum number of kills + deaths setting	None	This is the minimum number of kills + deaths a player needs in a round in order for that score to be counted towards their best round. This helps eliminate those 1-0 rounds where the score would be higher (infinite) than say a 35-1 round. This setting is changed on the config page, statistics tab. Applies to individual stat pages and player listings.
STAT_BEST_ROUND_KILLS	Statistics	All	Best round (num kills) a player had	None	Applies to individual stat pages and player listings.
STAT_BEST_ROUND_KILLS_MODIFIED	Statistics	Individual stat pages	Modified best round number of kills	Applies only to average stat generation	See STAT_KILL_STREAK_MODIFIED for a desciption of what these modified tags are for.
STAT_BEST_ROUND_KILLS_DEATHS	Statistics	All	Number of deaths the player had in their best round	None	Same as above
AVERAGE_STAT_BEST_ROUND_KILLS	Statistics	Individual stat pages	Number of kills in best round an average player scored	Applies only to average stat generation	Applies to individual stat pages only.
AVERAGE_STAT_BEST_ROUND_KILLS_DEATHS	Statistics	Individual stat pages	Number of deaths in best round an average player scored	Applies only to average stat generation	Applies to individual stat pages only.
AVERAGE_STAT_BEST_ROUND_KILLS_MODIFIED	Statistics	Individual stat pages	Modified best round number of kills	Applies only to average stat generation	See STAT_KILL_STREAK_MODIFIED for a desciption of what these modified tags are for.
STAT_BEST_ROUND_KILLS_DATE_TIME	Statistics	All	Date the player achieved their best round	None	Same as above
STAT_BEST_ROUND_KILLS_MAP_NAME	Statistics	All	Map the player achieved their best round on	None	Same as above
STAT_OVERALL_NUM_KILLS	Statistics	All	Total number of kills the player has	None	Same as above
STAT_OVERALL_NUM_DEATHS	Statistics	All	Total number of deaths the player has	None	Same as above
STAT_OVERALL_RATIO	Statistics	All	Overall K:D ratio of the player	None	Same as above
STAT_OVERALL_MINUTES	Statistics	All	Number of minutes the player has played	None	Same as above
STAT_OVERALL_KILLS_PER_MINUTE	Statistics	All	Kills per minute the player averages	None	Same as above
STAT_OVERALL_KILLS_PER_MINUTE_MODIFIED	Statistics	Individual stat pages	Modified kills per minute	Applies only to average stat generation	See STAT_KILL_STREAK_MODIFIED for a desciption of what these modified tags are for.
AVERAGE_STAT_OVERALL_KILLS_PER_MINUTE	Statistics	Individual stat pages	Kills per minute an average player scores	Applies only to average stat generation	Applies to individual stat pages only.
AVERAGE_STAT_OVERALL_KILLS_PER_MINUTE_MODIFIED	Statistics	Individual stat pages	Modified kills per minute an average player scores	Applies only to average stat generation	See STAT_KILL_STREAK_MODIFIED for a desciption of what these modified tags are for.
STAT_OVERALL_DEATHS_PER_MINUTE	Statistics	All	Deaths per minute the player averages	None	Same as above
STAT_OVERALL_DEATHS_PER_MINUTE_MODIFIED	Statistics	Individual stat pages	Modified deaths per minute	Applies only to average stat generation	See STAT_KILL_STREAK_MODIFIED for a desciption of what these modified tags are for.
AVERAGE_STAT_OVERALL_KILLS_PER_MINUTE	Statistics	Individual stat pages	Deaths per minute an average player scores	Applies only to average stat generation	Applies to individual stat pages only.
AVERAGE_STAT_OVERALL_KILLS_PER_MINUTE_MODIFIED	Statistics	Individual stat pages	Modified deaths per minute an average player scores	Applies only to average stat generation	See STAT_KILL_STREAK_MODIFIED for a desciption of what these modified tags are for.

HTML Tag	Category	Template Used in	Purpose	Dependencies	Notes
STAT_OPPONENT_HTML_FILE	Statistics	Individual stat pages	URL of opponent	Can only be in table block (see notes)	Specifies the URL (no directory, .html only) of the opponent's stat page. Stat is inserted into the block of HTML between STAT_xxx_FIVE_OPPONENTS_TABLE_BEGIN and STAT_xxx_FIVE_OPPONENTS_TABLE_END.
STAT_OPPONENT_NAME	Statistics	Individual stat pages	Name of the opponent	Can only be in table block (see notes)	Stat is inserted into the block of HTML between STAT_xxx_FIVE_OPPONENTS_TABLE_BEGIN and STAT_xxx_FIVE_OPPONENTS_TABLE_END.
STAT_OPPONENT_NUM_KILLS	Statistics	Individual stat pages	Number of kills against opponent	Can only be in table block (see notes)	Same as above
STAT_OPPONENT_NUM_DEATHS	Statistics	Individual stat pages	Number of deaths against opponent	Can only be in table block (see notes)	Same as above
STAT_OPPONENT_KD_RATIO	Statistics	Individual stat pages	Kill:Death ratio against opponent	Can only be in table block (see notes)	Same as above
STAT_WEAPON_NAME	Statistics	Individual stat pages	Weapon's name	Can only be in table block (see notes)	Stat is inserted into the block of HTML between STAT_WEAPONS_TABLE_BEGIN and STAT_WEAPONS_TABLE_END.
STAT_WEAPON_NUM_KILLS	Statistics	Individual stat pages	Number of kills player has with the weapon	Can only be in table block (see notes)	Same as above
STAT_WEAPON_KILL_PERCENTAGE	Statistics	Individual stat pages	Percentage of total kills this weapon accounts for	Can only be in table block (see notes)	Same as above
STAT_WEAPON_KILL_PERCENTAGE_INTEGER	Statistics	Individual stat pages	Modified percentage (as an integer) of total kills	None	The value inserted here is a modified value based on the Weapon Percentage Integer Multiplier application setting. The application takes the setting, multiplies it by the percentage the weapon accounts for, and then inserts the result into this tag. For example, say the player gets 48% of their kills via the SG-552. The Weapon Percentage Integer Multiplier is configured for 300. The application multiplies 300 by 0.48 to come up with 144. 144 is inserted into this tag when it comes time to displaying the SG-552. You can use this value for img widths, table widths, or anything of that nature, similar to what a bar graph would be using. Adjust the multiplier by going to the config screen when running the app if you want a larger/smaller number to be used. The percentage multiplier is basically the maximum value that can be returned (100%). Stat is inserted into the block of HTML between STAT_WEAPONS_TABLE_BEGIN and STAT_WEAPONS_TABLE_END.
STAT_WEAPON_NUM_DEATHS	Statistics	Individual stat pages	Number of deaths player has with the weapon	Can only be in table block (see notes)	Same as above
STAT_WEAPON_DEATH_PERCENTAGE	Statistics	Individual stat pages	Percentage of total deaths this weapon accounts for	Can only be in table block (see notes)	Same as above
STAT_WEAPON_DEATH_PERCENTAGE_INTEGER	Statistics	Individual stat pages	Modified percentage (as an integer) of total deaths	None	The value inserted here is a modified value based on the Weapon Percentage Integer Multiplier application setting. The application takes the setting, multiplies it by the percentage the weapon accounts for, and then inserts the result into this tag. For example, say the player gets 48% of their kills via the SG-552. The Weapon Percentage Integer Multiplier is configured for 300. The application multiplies 300 by 0.48 to come up with 144. 144 is inserted into this tag when it comes time to displaying the SG-552. You can use this value for img widths, table widths, or anything of that nature, similar to what a bar graph would be using. Adjust the multiplier by going to the config screen when running the app if you want a larger/smaller number to be used. The percentage multiplier is basically the maximum value that can be returned (100%). Stat is inserted into the block of HTML between STAT_WEAPONS_TABLE_BEGIN and STAT_WEAPONS_TABLE_END.

HTML Tag	Category	Template Used in	Purpose	Dependencies	Notes
INCLUDE_AVERAGE_SCORE_BEGIN	HTML code blocks	All	Marks beginning of average player code block	INCLUDE_AVERAGE_SCORE_END	This tag is used in conjuction with a matching INCLUDE_AVERAGE_SCORE_END tag. It marks code that should only be included when average stats are being calculated and inserted into the HTML. There is an option to not automatically generate average stats at the end of processing the log files, as it can add to the processing time. At the same time, however, the ability to generate individual web pages for players at the end of processing log files can be enabled. To keep the HTML that would show up only when average stats are being calculated from appearing otherwise, you would use these blocks. If the average stats aren't being included, the entire section is removed from the output. You would use this tag when you want HTML to be output that reflects stats with average comparison. When combined with the EXCLUDE_AVERAGE_SCORE_BEGIN block, the two blocks form a method by which you can vary the output according to whether average stats are being generated. For instance, you probably would not want a bar graph or average kills per minute stats in the HTML when average stats aren't available. On the other hand, you want HTML that just shows the player's score when average stats aren't available. See also EXCLUDE_AVERAGE_SCORE_BEGIN
INCLUDE_AVERAGE_SCORE_END	HTML code blocks	All	Marks end of average player code block	INCLUDE_AVERAGE_SCORE_END	See above. This is the end tag to a section of code to be included only when average stats are being calculated.
EXCLUDE_AVERAGE_SCORE_BEGIN	HTML code blocks	All	Marks beginning of player code block with no average stats	EXCLUDE_AVERAGE_SCORE_END	This tag is used in conjuction with a matching EXCLUDE_AVERAGE_SCORE_END tag. It marks HTML code that should only be included when average stats are NOT being calculated and inserted into the HTML. This is the opposite of what INCLUDE_AVERAGE_SCORE_BEGIN is for. You would use this tag when you want HTML to be output that reflects stats with no average comparison. When combined with the INCLUDE_AVERAGE_SCORE_BEGIN block, the two blocks form a method by which you can vary the output according to whether average stats are being generated. For instance, you probably would not want a bar graph or average kills per minute stats in the HTML when average stats aren't available. On the other hand, you want HTML that just shows the player's score when average stats aren't available. See also INCLUDE_AVERAGE_SCORE_BEGIN
EXCLUDE_AVERAGE_SCORE_END	HTML code blocks	All	Marks beginning of player code block with no average stats	EXCLUDE_AVERAGE_SCORE_BEGIN	See above. This is the end tag to a section of code to be included only when average stats are NOT being calculated.
STAT_TOP_FIVE_OPPONENTS_TABLE_BEGIN	HTML code blocks	Individual stat pages	Marks beginning of top-5 opponent code block	STAT_TOP_FIVE_OPPONENTS_TABLE_END	This tag marks the beginning of an HTML code block to be used as the row insertion for the top 5 opponents a player has faced. It is to be used in conjuction with a STAT_TOP_FIVE_OPPONENTS_TABLE_END tag to mark the section of code that will be repeated for up to 5 opponents. The app takes this section of code and copies it five times. For each of the top 5 opponents this player has faced, the app inserts the opponents name, then number of times the player killed the opponent, and the number of times the player was killed by the opponent. The app then inserts those 5 sections into the output HTML in the same location as where the block was grabbed from. You'd likely start a <table> before this block, and a </table> after the block, with your <tr>, <td> and such in between the block header and end. Applies to individual stat pages only. See the sample player template for an example. See also STAT_BOTTOM_FIVE_OPPONENTS_TABLE_BEGIN and Opponent Stats
STAT_TOP_FIVE_OPPONENTS_TABLE_END	HTML code blocks	Individual stat pages	Marks the end of top-5 opponent code block	STAT_TOP_FIVE_OPPONENTS_TABLE_BEGIN	See above. Marks the end of the top-5 opponent code block.
STAT_BOTTOM_FIVE_OPPONENTS_TABLE_BEGIN	HTML code blocks	Individual stat pages	Marks beginning of bottom-5 opponent code block	STAT_BOTTOM_FIVE_OPPONENTS_TABLE_END	This tag marks the beginning of an HTML code block to be used as the row insertion for the bottom 5 opponents a player has faced. It is to be used in conjuction with a STAT_BOTTOM_FIVE_OPPONENTS_TABLE_END tag to mark the section of code that will be repeated for up to 5 opponents. This works the same was as the top 5 block, except of course it's for listing the opponents that the player has had a tough time against. Applies to individual stat pages only. STAT_TOP_FIVE_OPPONENTS_TABLE_END. See the sample player template for an example. See also STAT_BOTTOM_FIVE_OPPONENTS_TABLE_BEGIN and Opponent Stats.
STAT_TOP_FIVE_OPPONENTS_TABLE_END	HTML code blocks	Individual stat pages	Marks the end of top-5 opponent code block	STAT_TOP_FIVE_OPPONENTS_TABLE_BEGIN	See above. Marks the end of the bottom-5 opponent code block.
STAT_OPPONENT_URL_LEFT_BEGIN	HTML code blocks	Individual stat pages	Marks the beginning of the opponent's left-side URL	STAT_OPPONENT_URL_LEFT_END	For opponents that do not meet the minimum requirements, this block is removed from the row so as to not generate a link. To be used in conjunction with STAT_OPPONENT_URL_LEFT_END, this marks the left side of the URL listing. Because the opponent's name appears in between the URL begin and end tags, it was necessary to split the block into two sections: left and right. For opponents that do meet the minimum requirements for their own web page, this tag is just left alone so the URL link is valid. See also STAT_OPPONENT_HTML_FILE and STAT_OPPONENT_URL_RIGHT_BEGIN.
STAT_OPPONENT_URL_LEFT_END	HTML code blocks	Individual stat pages	Marks the end of the opponent's left-side URL	STAT_OPPONENT_URL_LEFT_BEGIN	See above. Marks the end of the left-side of the URL listing.
STAT_OPPONENT_URL_RIGHT_BEGIN	HTML code blocks	Individual stat pages	Marks the beginning of the opponent's right-side URL	STAT_OPPONENT_URL_RIGHT_END	For opponents that do not meet the minimum requirements, this block is removed from the row so as to not generate a link. To be used in conjunction with STAT_OPPONENT_URL_RIGHT_END, this marks the right side of the URL listing. Because the opponent's name appears in between the URL begin and end tags, it was necessary to split the block into two sections: left and right. For opponents that do meet the minimum requirements for their own web page, this tag is just left alone so the URL link is valid. See also STAT_OPPONENT_HTML_FILE and STAT_OPPONENT_URL_LEFT_BEGIN
STAT_OPPONENT_URL_RIGHT_END	HTML code blocks	Individual stat pages	Marks the end of the opponent's URL	STAT_OPPONENT_URL_RIGHT_BEGIN	See above. Marks the end of the right-side of the URL listing.
STAT_WEAPONS_TABLE_BEGIN	HTML code blocks	Individual stat pages	Marks the beginning of the weapon distribution table	STAT_WEAPONS_TABLE_END	This tag, in conjuction with STAT_WEAPONS_TABLE_END, marks the block of code where the weapon distribution table is inserted. For every weapon that this player has either killed someone with or has been killed by someone with, the app inserts the block of code with replacments for the weapon name, the number of kills, the percentage of kills, the number of deaths, and the percentage of deaths. Like the other table blocks, you'd start with a <table> before the block, a </table> after the block, and <tr>/<td> items to mark each row that should be inserted. See Weapon Stats for the list of tags that go in between this section.
PLAYER_LIST_TABLE_BEGIN	HTML code blocks	Individual stat pages	Marks the beginning of the player listing table	PLAYER_LIST_TABLE_END	This tag, in conjuction with PLAYER_LIST_TABLE_END, marks the block of code where each player gets listed in the Player Listings. For each player that will be listed, the app inserts various information about that player into the row the block details. Every player statistic can be used in the listings, so that you can show stats beyond what the list is sorting. Like the other table blocks, you'd start with a <table> before the block, a </table> after the block, and <tr>/<td> items to mark each row that should be inserted. See Player Stats for the list of tags that go in between this section. See also the Player List Maximum application setting to set the maximum number of players that will be output with the listing. See SETTING_PLAYER_LIST_MAXIMUM for the tag to insert this setting.