Edited by DarthPeanut, 05 October 2014 - 12:32 PM.
"destroyed By"... (Blank)
#1
Posted 05 October 2014 - 12:30 PM
#2
Posted 05 October 2014 - 12:32 PM
I've had it a few times when I've been clipped by a turret when I'm nearly cored and it's ended me, resulting in either the ones it hit me with, or ALL damage reading blank.
#3
Posted 05 October 2014 - 12:33 PM
Edited by DarthPeanut, 05 October 2014 - 12:36 PM.
#4
Posted 05 October 2014 - 12:40 PM
#5
Posted 05 October 2014 - 12:42 PM
#6
Posted 05 October 2014 - 12:43 PM
Of course it is hard to say without knowing what your damage conditions were and a bunch of other factors.
#7
Posted 05 October 2014 - 12:54 PM
Edited by DarthPeanut, 05 October 2014 - 12:56 PM.
#8
Posted 05 October 2014 - 01:01 PM
#9
Posted 05 October 2014 - 01:03 PM
DarthPeanut, on 05 October 2014 - 12:54 PM, said:
You were destroyed by ghost damage, the sneaky cousin of ghost heat. Don't forget to burn some incense before initiating a gaming session to scare away the ghosts...
#10
Posted 05 October 2014 - 01:06 PM
Nathan Foxbane, on 05 October 2014 - 12:43 PM, said:
Of course it is hard to say without knowing what your damage conditions were and a bunch of other factors.
If the collision was with another mech, that mech may get the credit. I pulled off a Death From Above once doing this (Entirely on accident, I landed on an enemy victor I never shot, and got a Kill).
Edited by Bront, 05 October 2014 - 01:06 PM.
#11
Posted 05 October 2014 - 01:08 PM
DarthPeanut, on 05 October 2014 - 12:33 PM, said:
That does not look like anywhere near the dropship's tail, looks more like you were near one of the cap points. If I had to guess, I'd say you and the other team somehow switched sides of the dropship during the fighting, and you somehow got the attention of a missile turret. The missile turrets seem to have a range of around 1200 meters, but I've never conclusively documented it.
That or just a weird bug where the database dropped damage source info.
#12
Posted 05 October 2014 - 01:13 PM
Escef, on 05 October 2014 - 01:08 PM, said:
That or just a weird bug where the database dropped damage source info.
They only hit at 1000, but they seem to start firing at around 1200. Perks of infinite ammo bins I guess. Be hilarious if they actually had ammo limits.
Still do not know the damage condition of the OP's 'Mech before. If internals were exposed or not.
Edited by Nathan Foxbane, 05 October 2014 - 01:16 PM.
#13
Posted 05 October 2014 - 01:16 PM
Escef, on 05 October 2014 - 01:08 PM, said:
I have seen that before in non-base matches. I also noticed I have stats for weapons where I played 0 games with that weapon somehow. I think it may be some DB Data dropping (might also explain why I'm missing 2 of my 130 point wins)
#14
Posted 05 October 2014 - 01:16 PM
Nathan Foxbane, on 05 October 2014 - 01:01 PM, said:
Which is why I posted. Very strange and I did not have a clue either.
Escef, on 05 October 2014 - 01:08 PM, said:
That or just a weird bug where the database dropped damage source info.
We pushed over saddle... they went lower city hook. That is on the back side of the saddle by the tail of the dropship in that cluster of 5-6 buildings. Skirmish... no turrets.
That is the drop ship you can see in the background right side. Saddle is in the distance straight ahead in that view. Hard to get a clear shot with the spinning camera view of death.
Edited by DarthPeanut, 05 October 2014 - 01:18 PM.
#15
Posted 05 October 2014 - 01:20 PM
DarthPeanut, on 05 October 2014 - 01:16 PM, said:
Yes, the middle of the dropship by the looks of it, which would place you nowhere near the tail.
But if you were in skirmish than turrets are right out, so the only explanation seems to be a database error of some kind.
#16
Posted 05 October 2014 - 01:39 PM
Escef, on 05 October 2014 - 01:20 PM, said:
But if you were in skirmish than turrets are right out, so the only explanation seems to be a database error of some kind.
Well midway between the split in it and the tail... approximately.
There are no turrets in skirmish so yea.
Edited by DarthPeanut, 05 October 2014 - 01:41 PM.
#17
Posted 05 October 2014 - 03:00 PM
Nathan Foxbane, on 05 October 2014 - 12:43 PM, said:
Of course it is hard to say without knowing what your damage conditions were and a bunch of other factors.
Collision damage is actually listed; not blank.
Not sure what would cause this.
#18
Posted 05 October 2014 - 03:02 PM
#20
Posted 05 October 2014 - 03:21 PM
(Just a joke, please no one take offense.)
Edited by DarthPeanut, 05 October 2014 - 03:21 PM.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users