ProjectTako / kparser

Automatically exported from code.google.com/p/kparser
1 stars 3 forks source link

Damage on damage details not showing on colidated info #23

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Larger Parse File:  IE:  J.Lo / Kirin / Einherjar
2. Many members.  Full alliance +

What is the expected output? What do you see instead?
I expected damage totals to include all damage output from all members
under the Offense tab.  This was not the case.  There were individuals in
the Damage: Details tab who were not included in the consolidated information.

What version of the product are you using? On what operating system?
Vista 32.

Please provide any additional information below.
Please see Neosutra in the attached parse file, dealing damage to J.Lo in
the details via Shield bash and Atonement.  Yet he will not be in the
damage totals.

Original issue reported on code.google.com by GTHje...@gmail.com on 17 Jan 2009 at 10:01

Attachments:

GoogleCodeExporter commented 8 years ago
Have determined that this is an issue in the parsing. Specifically, this is 
related
to charmed players getting entered as 'mob' combatants, and then once uncharmed 
all
further parse data for that player defaults to linking to the mob version of 
the name
instead of the player version.

The Details page doesn't filter for mob vs player so it still shows all details,
while the basic Offense page filters combatants to include players/pets/npcs 
only,
and thus doesn't show that additional detail. 

Further work will be needed to fix the underlying problem.

Original comment by Kinemati...@gmail.com on 27 Jan 2009 at 1:30

GoogleCodeExporter commented 8 years ago
Changed status.

Original comment by Kinemati...@gmail.com on 27 Jan 2009 at 1:30

GoogleCodeExporter commented 8 years ago
Thank you for accepting and working on my problem ticket.  That is an amazing 
tracing of the underlying problem to result in the parse.  Keep up the good 
work!

Original comment by GTHje...@gmail.com on 17 Feb 2009 at 5:24

GoogleCodeExporter commented 8 years ago
Fixed in 1.3.0a.  You can reparse the above JLo file to check that it shows the
proper damage.

Original comment by Kinemati...@gmail.com on 16 Mar 2009 at 8:49