Tremolo4 / stasiscl

Automatically exported from code.google.com/p/stasiscl
0 stars 0 forks source link

I can't get Razorscale kill to parse #130

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What exactly went wrong? Was a particular stat reported incorrectly, was a 
raider assigned the 
wrong class or pets, was a log split up improperly, or was it something else? 
Please be as 
specific as you can with regard to particular fights, players, pets, or mobs.

It skips this kill and all attempts, XT002 went fine though.

Were there any error messages or warnings on the console when you ran the 
program?

No

NOTE: Please be prepared to send a copy of the combat log that caused you 
trouble. If you 
would like to post it now, please zip it first to save space.

Here is the Kill line:
4/15 20:23:26.523  
UNIT_DIED,0x0000000000000000,nil,0x80000000,0xF1300081A201A50D,"Razorscale",0x30
a4
8

I will attach the entire log, but I deleted all of the XT-002 stuff

Original issue reported on code.google.com by 19vett...@gmail.com on 16 Apr 2009 at 6:34

Attachments:

GoogleCodeExporter commented 9 years ago
I was using r252

Original comment by 19vett...@gmail.com on 16 Apr 2009 at 6:35

GoogleCodeExporter commented 9 years ago
Do a new checkout. The revision of stasis didn't change, but there were updates 
to
some files in /lib. Notably logsplit.pm. This fixed my problem.

Now if only we can see what our vehicles do, to see who fails on Flame Levi 
(and Malygos)

Original comment by steverun...@gmail.com on 16 Apr 2009 at 2:33

GoogleCodeExporter commented 9 years ago
Hmmm...I did 2 checkouts last night, then another tonight and it worked....hmmmm

well, it worked, case closed...thanks for your work

Original comment by 19vett...@gmail.com on 17 Apr 2009 at 12:53

GoogleCodeExporter commented 9 years ago
Good to know :)

Original comment by gianmerlino@gmail.com on 17 Apr 2009 at 2:27