search

ProjectTako / kparser

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

another problem with HELM tracking. #20

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Go Mining 
2. look at the parse vs what you dig up 

What is the expected output? What do you see instead?
i expected it to give me an accurate running total of my digs, but it looks
like it is failing to read one of the ways that the game displays the
results.  i think it's the "you get this but your that breaks" since i had
one of those and my break total went up, but my dig total did not. 
something isn't being parsed right.

What version of the product are you using? On what operating system?
1.6.1.1 i believe... whichever had the logging bug fixed in it.

Please provide any additional information below.
i don't mean to be a bother... but i'm trying to keep track of the % so i
can update the wiki with more accurate numbers and numbers for the HELM gear.

Original issue reported on code.google.com by Adal...@gmail.com on 15 Nov 2008 at 8:15

GoogleCodeExporter commented 8 years ago 
just checked it again, and it's for sure that it's not reading the items you 
get when
your tool breaks.  just got a break on a copper ore and it incremented the break
total, but not my copper ore or my total tries.

Original comment by Adal...@gmail.com on 15 Nov 2008 at 8:19

GoogleCodeExporter commented 8 years ago 
Can you provide the exact message you see that isn't being logged?  Current 
parsing
expects something like "You dig up a pebble, but your pickaxe breaks."

Original comment by Kinemati...@gmail.com on 2 Dec 2008 at 4:14

GoogleCodeExporter commented 8 years ago 
this might be old news, but I am having the same issue with helm results as 
Adalast.
the information that comes into the log that you're looking for regarding 
breaking
tools but still getting materials to turn out is:

You dig up a flint stone, but your pickaxe breaks in the process.

usually kparse will signify this as a straight break each time this event 
occurs.
(currently using kparse 1.2.0.0)

Original comment by zer0_ph...@earthlink.net on 15 Jan 2009 at 8:47

GoogleCodeExporter commented 8 years ago 
Fixed regex for finding successful HELM results that also had a tool break.

Original comment by Kinemati...@gmail.com on 5 Feb 2009 at 7:09