ProjectTako / kparser

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

Issue with Ouryu parse #54

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Parse the battle "Ouryu Cometh" (parsed using Kparser 1.3.6) using
"Begin Default Parse".  Quit parsing.
2. Attempt to isolate damage done to Ouryu in the Offense tab by selecting
"Ouryu (0)" from the Mobs menu.

What is the expected output? What do you see instead?
I was hoping to see just the damage done to Ouryu.  Instead, 1.3.6 will
cause an "Unhandled Exception".  When loading the saved parse on 1.4.2 and
1.4.4, nothing will happen; no exception dialog will appear, but the
Offense tab will continue to display whatever it was last displaying.

What version of the product are you using? On what operating system?
1.3.6, 1.4.2, and 1.4.4 on 32-bit Windows Vista.

Please provide any additional information below.
I have two Ouryu parses that cause this issue, and one that works
correctly; I can't really tell why.  I've attached the latest non-working
one.  The parse was collected using 1.3.6, as I still can't get any 1.4.x
versions to work when parsing live data (separate issue).

Original issue reported on code.google.com by ray.v.s...@gmail.com on 9 Nov 2009 at 4:46

Attachments:

GoogleCodeExporter commented 8 years ago
Should be fixed in 1.4.5.  Better handling of player/mob identification should 
avoid
instances where it thinks they're actually charmed mobs/players.

Original comment by Kinemati...@gmail.com on 10 Nov 2009 at 5:46