Open GoogleCodeExporter opened 8 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
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
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
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
Original issue reported on code.google.com by
h...@proc.ru
on 17 Apr 2009 at 6:36