0x000000000486480C displaying on player history page

[GoogleCodeExporter]

for some reason 0x000000000486480C was added to the player history page, if 
needed i can swift thru which log file created it. you can see it at 
http://sws.exodus-kt.com

Original issue reported on code.google.com by yahwec...@gmail.com on 1 Dec 2008 at 9:35

[GoogleCodeExporter]

Please attach the log file, zipped if you can.

Original comment by gianmerlino@gmail.com on 1 Dec 2008 at 10:51

[GoogleCodeExporter]

check http://www.exodus-kt.com/tmp/combatlog.zip

sorry for such long reply, had to sort thru all these combat logs to find out 
whihc 
one it was.

Original comment by yahwec...@gmail.com on 3 Dec 2008 at 8:55

[GoogleCodeExporter]

Can't seem to download that file, I'm getting a not found message. Try 
attaching it directly here, there should be 
an "attach a file" link.

Original comment by gianmerlino@gmail.com on 6 Dec 2008 at 8:39

[GoogleCodeExporter]

Original comment by gianmerlino@gmail.com on 6 Dec 2008 at 8:40

• Changed state: Accepted

[GoogleCodeExporter]

plz try http://www.exodus-kt.com/tmp/combatlog.zip again, sorry must have been 
deleted.. the attachment is too big i get an error everytime i finish uploading 

Original comment by yahwec...@gmail.com on 13 Dec 2008 at 2:42

[GoogleCodeExporter]

Hello, I've had something similar.
Report here: http://207.134.134.223:51279/sws-patchwerk-1232680082/index.html

After some checking it seems that this 'number player' is a fake owner of the
doomguard of the warlock named ionas. Can't see its damage in the ionas page 
but if
you go to the raid and mobs page the doomguard is there and is marked to be the 
pet
of this famous 'number player' instead of ionas

Original comment by traveltoaiur on 23 Jan 2009 at 5:59

[GoogleCodeExporter]

report here: http://reports.ueguild.com/cl.rar
sorry it's pretty big, there's like 3 raids in it.

Original comment by traveltoaiur on 23 Jan 2009 at 6:09

[GoogleCodeExporter]

Original comment by gianmerlino@gmail.com on 23 Jan 2009 at 6:55

[GoogleCodeExporter]

ok, the strange player has disappeared with the last fixes you applied so far!
however the doomguard here now has no owner instead of being marked as ionas' 
pet.

I guess this is because there was another warlock in the combat log who 
summoned a
doomguard before and both doomguards have the same name and so your tool can not
determine anymore whose doomguard it was.

Not sure how everything is handled, but isn't there an guid given to a doomguard
which is constant to be able to assign it to someone? Like if I summon a 
doomguard
twice, will these two doomguards have the same ID or will it differ since we're 
not
summoning the old one back but a new one?

Aww, sorry for my english, hope you got my point.
Keep up the good work, the libraries you made are awesome

Original comment by traveltoaiur on 24 Jan 2009 at 4:22

[GoogleCodeExporter]

Yeah, I am pretty sure that your analysis was right, and these unindexed 
players appear when a pet is present 
without its owner (or at least, what stasiscl thinks the owner is). I made 
doomguard assignment a little more 
conservative in the last revision, so that's why the mystery player disappeared 
(it used to assign all doomguards 
to the same person if it only saw one person summoning them, now it no longer 
does that).

The only way you can associate doomguards with their owners right now is by 
looking for some magic that 
happens when they are summoned, so if you miss a summon (like, the logger is 
not around to see the summon 
happen) the doomguard won't be associated with the lock.

Original comment by gianmerlino@gmail.com on 24 Jan 2009 at 5:43