Important stuff:

• Don't edit the log file... at all.
• To save: right click anywhere on the page and click on 'Save Page As'. From here give the file whatever name you want, but make sure to change 'Save as type' to 'Web Page, HTML Only'. From there click save and host it to any webserver.

Features:

• This parser automatically detects both setup rounds and dead rounds, making it easier on people who don't know how or what they used to need to remove. If by chance you do encounter a setup or dead round parsed, please send me the log by email along with what round it was so that I may refine how they are detected and removed.
• Overtime is fully supported* for CAL games, no need to split the log and send in 2 or 3 separately. The parser will automatically detect when overtime is reached and start writing down wich overtime the match has reached, along with the current round of that overtime. - thanks to Joe131 for the idea.
• Map is automatically detected by the parser.
• Putting a team banner at the top of the page is an option.
• League pictures are automatically added.
• An option to name a game MVP has been put in. Game MVP's will have a small yellow star next to their name on all tables and have a colored top line on the detailed stats mini-page.
• Player country flags have been implemented, and display automatically on the advanced stats mini-page. - thanks to GeNeRaL for the idea.
• Comprehensive stats are shown when you scroll over a players name on the bottom table of the generated page. These state include how many kills the player had on both teams, number of aces, suicides, who he has killed and how many times.

*Overtime support notes:

• Overtime is supported in this parser. The only problem is that tournament mode ends after a match reaches the final regular play round. I have included OT support for people who don't want to have two seperate log files, and for the possibility of TM being fixed in the future.
• To insert the OT rounds from one log to the other, you need to paste in from the first 'ScriptLog' (NOT 'DevNet') all the way to the end from the second log file. It is also needed that you remove all player left messages from the first log before you paste in the OT rounds. Oh and yes I see how this goes aginst the whole "don't edit the log file" thing I have written everywhere, this is just an exception ;)
• TWL and HTGN game logs will not have OT supported for the simple reason that OT on TWL is always a different map, and this parser is simply not built to offer multi-map support. If you add OT rounds to a log for a TWL or HTGN match, they will show what overtime it is and what round correctly, but it till not update the sides that the teams are on correctly. I suggest for you to re-parse OT rounds seperatly when it comes to TWL and HTGN matches.
• For OT to work, teams must go back to their original sides, otherwise, it won't work.

How to use:

• If this is your first time using the parser, you may not know exactly what a log is. AA logs are automaticly generated after each session and are usualy put in your AA servers' /logs/ folder. You need to retreive the log from the match you played (usually the last one) and upload it into this parser. Do not open/view the file in a text editor then save it, this may cause problems, instead just drag & drop it to your desktop or wherever you want. If you're FTP client does not support drag & drop, I suggest you get a new one. I use FileZilla (Free).
• DO NOT edit your log file! This parser is made to handle the raw unchanged log that your server gives out. The only reason to edit your log before sending it in is if my parser makes a mistake somwhere (it shouldn't :P), somebody took 4 days to leave the server and it added a extra round for nothing at the end, or you feel like making yourself look more e-cool and giving yourself more kills.
• Make sure you put in the right teams when asked for it. Make use of the table on the bottom of the submit page, it tells you exactly what you need for the odd team named maps.
• Make sure when you type your MVP that you type it 100% correctly. Yeah that's right, CaSe-SeNsItIvE!
• Max log size is 50K bytes. If your log is bigger then this, you need to take a break from the game.
• Only allowed log files end in .log or .txt. All other file type will be rejected.
• To save: right click anywhere on the page and click on 'Save Page As'. From here give the file whatever name you want, but make sure to change 'Save as type' to 'Web Page, HTML Only'. From there click save and host it to any webserver.
• Read this page on how to host the log files: HowToHost.php
• No HTML or other programming language in the text boxes, they have been fited so all code is removed.
• Spread the word! The more people that use this, the happier I am :)

General notes & requests to the user:

• If a death message is 'has been killed by' instead of has been shot by, or sniped by, please send that log in to me in a email along with what round it happened. This is caused by a kill by a weapon that I did not anticipate/came across when going through killing people in a server with all weapons I could. followed by ripping apart the logs getting all the kill messages.
• Unlike other parsers, this one does not make mistakes in deaths and kills. I have sent log files through the iog parser, the ENE parser, and mine, then made sure of all the information was correct, going kill by kill making sure EVERYTHING added up. Though the iog and ENE ones where often right on the money, they sometimes added an extra death for causes unknown. I have yet to see my parser add anything that shouldn't be there. If you come across any errors, please email me ASAP so it may be fixed.
• I put in clear to see HTML comments in the parsed page. These comments show exactly where one round starts, and the other begins, and also where individual player stats start too. The comments will look like this:
  
  I did this in case of something like this happening:
  
  If somebody takes his time leaving the server, it may result in a extra round showing, all you need to do is go in and delete from the first comment to the second. Easy wasn't it?
• I removed support of join/leave messages on style 3 because it looked uglier then sin
  

Everything Else:

What does count as a kill:

• killing an enemy player

What doesn't count as a kill:

• TK
• Suicide

What counts as a death:

• Leaving a crater
• Bleeding out
• Getting TKed
• Suicide

What doesn't count as a death:

• Leaving server

• Nading yourself
• Leaving a crater

What doesn't count as a suicide:

• Bleeding out

Contact info:
Marc Ashman
email & MSN: marc(dot)ashman(at)gmail(dot)com