Why would I use KParser instead of other parsers? Parsers that I have previously used tend to cater solely to people jacking off to how much damage they do in a parsing session; their output doesn't tell you anything about the proportion of the monster's attention that each damage-dealer commands, which might be worth considering before one makes ridiculous generalizations regarding the relative effectiveness of a job combination or equipment set. In contrast, the sophisticated KParser actually crunches detailed numbers for defensive statistics (among other things, too many to discuss briefly)! KParser is not only interesting enough to keep me from being bored to tears, but it's also a pretty neat diagnostic tool to help me delve deeper into a parsed situation.
I put KParser to the test during a pickup merit party at Tadjana Isle (Greater Colibri with the occasional Mamool Ja mixed in) with the following party configuration:
Myself as WAR/NIN #1: used Perdu Voulge exclusively; 12% Haste (Walahra Turban, Swift Belt, Dusk Gloves), mediocre WS equipment.
WAR/NIN #2: Used both Byakko's Axe and some dual-wield combo with main-hand axe, at least 17% haste probably.
WAR/NIN #3: Maneater/Ridill, Adaman Hauberk, at least 17% haste probably. (Kupo member.)
WAR/NIN #4: Maneater/Juggernaut, Ares's Cuirass, at least 17% haste probably.
RDM and BRD/NIN
Looking at the offensive numbers alone (102 monsters, 19,385 experience points over 1:09), I can't really conclude that any of the warriors is loafing; our damage proportions are within 5% of one another (this is just a rule of thumb of mine, not based on any statistical criterion):
Damage Summary
Player Total Dmg Damage % Melee Dmg WSkill Dmg
WAR/NIN #1 124488 26.17 % 74760 49728
WAR/NIN #2 108562 22.82 % 73771 34736
WAR/NIN #3 112252 23.60 % 77009 35242
RDM 1080 0.23 % 926 153
WAR/NIN #4 128528 27.02 % 85934 42582
SC: Reverberation 776 0.16 % 0 0
Total 475686 100.00 % 312400 162441
However, looking at the numbers for "attacks against," we see here that WAR/NIN #3 (Maneater/Ridill) took the fewest attacks of all the damage-dealers:
Attacks Against:
Player Total Attack# % Avoided Avoid %
WAR/NIN #1 174 24.58 % 145 83.33 %
WAR/NIN #2 118 16.67 % 85 72.03 %
WAR/NIN #3 83 11.72 % 54 65.06 %
RDM 8 1.13 % 1 12.50 %
WAR/NIN #4 179 25.28 % 142 79.33 %
BRD/NIN 146 20.62 % 113 77.40 %
KParser even has a distinct category for Utsusemi casting. Notice that WAR/NIN #4 (Maneater/Juggernaut, Ares's Cuirass) cast Utsusemi: Ichi 25 times during the 1 hour, 9 minute session, which may have had a deleterious effect on his damage output:
Utsusemi
Player Shadows Used Ichi Cast Ichi Fin Ni Cast Ni Fin
WAR/NIN #1 133 15 11 48 43
WAR/NIN #2 72 4 4 34 30
WAR/NIN #3 49 4 4 28 24
RDM 1 0 0 0 0
WAR/NIN #4 130 25 19 44 42
BRD/NIN 112 4 4 43 40
The best feature of all is KParser's ability to filter types of chat, including Arena and NPC chat! Well, it can help when you want to review NPC dialogue by filtering out annoying /party and /shout crap. It could also be useful to revisit what someone said in /tell that you happened to gloss over hundreds of chat lines ago.
From a meriting standpoint, I don't use parsers to make sweeping, erroneous generalizations but as a diagnostic tool to help me fine-tune my own performance. There isn't much of a take-home message from a typical parse of a merit party; all I really care about is that the group as a whole is getting the job done and that I am pulling my own weight.
As far as soloing concerns go, of my outlandish, totally unrealistic "ninja solo" goals is to acquire the items chest on the second floor of SE Apollyon. KParser can help me determine the (lack of) effectiveness of my evasion setup and (poor) dagger accuracy when fighting the Adamantshells, and also the average time spent fighting each Adamantshell.
Note: parser output was truncated for clarity.