[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace() [function.preg-replace.php]: The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4759: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3887)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4761: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3887)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4762: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3887)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4763: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3887)
=69.GIAP=SQUAD Forums • View topic - The 69 GIAP RoF Text Log Parser How-To

The 69 GIAP RoF Text Log Parser How-To

Join us in turning the clock back.

Moderator: =69.GIAP=Members

The 69 GIAP RoF Text Log Parser How-To

Postby =69.GIAP=TUSHKA » Sun Mar 31, 2013 4:32 am

OK, I first wrote these instructions for Stenka, but they should work for anyone who wants to use our parser. It is available for anyone who wants to us it, or to improve it.

It is a bit fussy, but simple enough.

First you will need to set some things up.

The parser itself is written in PHP, so it needs a PHP-enabled web server.

If you have access to one, you are good to go. In my case I use my home UNIX box, but it doesn't matter where it is just so you have full access to it.

You will be able to grab the files you need from


The important ones are readme (with simple instructions), copy.bat (which will be placed on the game server), parse.php (the parser itself) and whichever location.csv files you need for your campaign which will be placed on the php-enabled web server.

You will also need to configure your game server to save text log files. Instructions can be found in the startup.cfg.settings file.

Once you have startup.cfg configured and have placed copy.bat in the server's data directory you are ready to run a mission and analyze the logs.

Phase one is to create the mission report from the log text files.

This consists of a few steps.

Go to Rise of Flight/data and delete all the log text files that are from old missions and the warm-up, etc leaving just the ones from the mission. Each mission is time-stamped by the time it was started, then numbered from zero to the final log file, generally in the area of 200 or so. Remove any files of the format missionReport(.....).txt that are *not* from the mission you want to analyze.

Next click on "copy.bat" in the same directory. This will put all the single-digit files into MissionReport1.txt, the two-digit files into MissionReport2.txt, and three-digit files into MissionReport3.txt and then combine all of these, in order into MissionReport.txt.

Delete the two or three numbered files (so they won't be included accidentally into the next report) and rename MissionReport.txt appropriately... i.e. to something like MissionReportYankeeDoodle14.txt.

Phase two is to analyze the log file.

Transfer the renamed logfile to the machine where you have installed parse.php (I email it to myself).

parse.php is the parser. It needs to be installed on a machine that has a php-enabled web server because it presents the report as a simple web page. i.e. you go to http://your.server.com/rof/parse.php to see the report. An appropriate locations.csv file also needs to be in that same directory. It can be edited as needed to match your campaign (e.g. different borders or front-lines).

You will need to edit the top of parse.php to indicate that this is a Yankee Doodle mission by setting the appropriate Campaign variable ($YANKEEDOODLE) to 1 (and the others to 0), then set $LOGFILE to the name of the logfile which you have now placed in the same directory as parse.php. Obviously you can configure it for other campaigns also or roll your own. See the code for examples,

Save these changes.

Then you go to the page and copy-paste the result into a posting in our Rise of Flight forum.

I'll update parse.php from time-to-time with improved internal instructions and provisions for new content to make this as fool-proof as possible.

Best wishes,
Tushka
Last edited by =69.GIAP=TUSHKA on Tue Apr 02, 2013 7:30 pm, edited 1 time in total.
C!

Tushka

Flying isn't dangerous. Crashing is what's dangerous.

User avatar
=69.GIAP=TUSHKA
 
Posts: 4048
Joined: Sat Jun 14, 2008 11:44 pm
Location: The Democratic People's Republic of Ohio

Postby BH_von Guber » Sun Mar 31, 2013 5:10 am

Thank you very much Tushka! Very good of you to make this available.
BH_von Guber
 
Posts: 8
Joined: Wed Sep 26, 2012 12:30 am
Location: New Mexico

Postby =69.GIAP=STENKA » Tue Apr 02, 2013 3:02 pm

Tushka,

didn't we need some sort of csv file with map locations in?
Baaaaaaaaagh!

User avatar
=69.GIAP=STENKA
 
Posts: 2273
Joined: Mon Jun 16, 2008 7:22 pm
Location: Paris

Postby =69.GIAP=TUSHKA » Tue Apr 02, 2013 7:33 pm

C!

Tushka

Flying isn't dangerous. Crashing is what's dangerous.

User avatar
=69.GIAP=TUSHKA
 
Posts: 4048
Joined: Sat Jun 14, 2008 11:44 pm
Location: The Democratic People's Republic of Ohio

Postby BH_von Guber » Tue Apr 02, 2013 8:50 pm

BH_von Guber
 
Posts: 8
Joined: Wed Sep 26, 2012 12:30 am
Location: New Mexico

Postby =69.GIAP=TUSHKA » Tue Apr 02, 2013 9:09 pm

C!

Tushka

Flying isn't dangerous. Crashing is what's dangerous.

User avatar
=69.GIAP=TUSHKA
 
Posts: 4048
Joined: Sat Jun 14, 2008 11:44 pm
Location: The Democratic People's Republic of Ohio

Postby BH_von Guber » Wed Apr 03, 2013 2:36 am

BH_von Guber
 
Posts: 8
Joined: Wed Sep 26, 2012 12:30 am
Location: New Mexico

Postby =69.GIAP=TUSHKA » Wed Apr 03, 2013 5:45 am

C!

Tushka

Flying isn't dangerous. Crashing is what's dangerous.

User avatar
=69.GIAP=TUSHKA
 
Posts: 4048
Joined: Sat Jun 14, 2008 11:44 pm
Location: The Democratic People's Republic of Ohio


Return to Rise of Flight

Who is online

Users browsing this forum: No registered users and 1 guest

cron