Xadras / stasiscl

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

Flame Leviathan report is empty #133

Open GoogleCodeExporter opened 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.

I make report with latest revision (r252) for two bosses - Leviathan+X002, 
first of one "Flame Leviathan" damage out/in are empty - http://
wws.proc.ru/raid-20090416_2107/
we playing on RU servers, maybe this cause problem.
report was generated by command

perl stasis \
    add -dir "$REPORTSDIR/$folder" \
    -file "$srclog" \
    -attempt \
    -minlength 2 \
    -overall \
    -locale C \
    $stasis_extra_opts \
|| exit 1

Were there any error messages or warnings on the console when you ran the 
program?
i have a lot of warning during report - "Wide character in print at lib/
Stasis/CLI/Writer.pm line 227, <INPUT> line 40165", line number increasing

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.

archived log - http://wws.proc.ru/logs/WoWCombatLog-20090416_2107.txt.bz2

Original issue reported on code.google.com by h...@proc.ru on 17 Apr 2009 at 6:36

GoogleCodeExporter commented 9 years ago
seems to be by design bug. in combatlog no palyername during machine control 
(sorry 
for ru translation)

4/16 21:19:12.914  SPELL_DAMAGE,0xF15000818F05A17C,"Механическое 
сиденье в трофейном 
разрушителе",0x1111,0xF1300085BA05A336,"Испещренный 
рунами 
часовой",0xa48,62635,"Пушечный 
залп",0x4,6466,0,4,719,0,0,nil,nil,nil
4/16 21:19:12.963  SPELL_DAMAGE,0xF15000812605A2CD,"Трофейный 
чоппер",0x1112,0xF13000832405DA88,"Кованый 
защитник",0xa48,62974,"Ультразвуковой 
рожок",0x1,5605,0,1,0,0,0,nil,nil,nil
4/16 21:19:12.963  SPELL_CAST_SUCCESS,0xF15000812405A16A,"Трофейная 
осадная 
машина",0x1114,0x0000000000000000,nil,0x80000000,62346,"Паровое 
ускорение",0x1
4/16 21:19:12.963  SPELL_DAMAGE,0xF15000812605A2CD,"Трофейный 
чоппер",0x1112,0xF13000832405DA70,"Кованый 
защитник",0xa48,62974,"Ультразвуковой 
рожок",0x1,10530,0,1,0,0,0,1,nil,nil
4/16 21:19:13.119  
SPELL_CAST_FAILED,0x0700000000FAD0AF,"Иож",0x511,0x0000000000000000,nil,0x800
00000,62634,"Пушечный 
залп",0x4,"Еще не готово."

Original comment by h...@proc.ru on 17 Apr 2009 at 11:54

GoogleCodeExporter commented 9 years ago
I was hoping that when 3.1 was released Blizz would make the change to 
incorporate
some sort of tie between vehicles and the controlling character.  Currently you 
can
typically tell from looking at your own log which vehicle is yours, but have no
information as to who is controlling the other vehicles.

Original comment by celibate...@gmail.com on 20 Apr 2009 at 8:28

GoogleCodeExporter commented 9 years ago
In my experience the (one 25 man and two 10 man flame leviathan runs), the 
parses
only include data for:

* players that where outside of an vehicle (people thrown on top of him for 
instance,
they're non-vehicle damage is reported correctly as far as I can tell)
* the player who is logging (shows as no damage though since I was driving the 
entire
fight)

Original comment by mwaf.m...@gmail.com on 21 Apr 2009 at 10:31

GoogleCodeExporter commented 9 years ago
Oddly enough last night I was getting information from Vehicles in Recount that 
was
attributing the damage to the controller of the vehicle. No idea if it was just
guessing but it seemed to be accurate.

Original comment by richard%...@gtempaccount.com on 1 May 2009 at 3:54