35 replies to this topic

[Roadbuster]

Did someone else notice mechs just blowing up without giving the attacker the kill lately?
I've seen (when spectating) and had it happen (when killing a mech myself) a number of times in the last few days.
Seems like these pilots put ammunition in their CT to die from ammo explosion.
Do deaths through ammo explosion not count as kills for the attacker?

The times I've seen that happen none of the mechs had enough time to build enough heat to die from overheating, but the attacker didn't fire the killing shot either.
So, I guess what's happening is an ammo explosion.
Some matches ended with 12 mechs destroyed but only 8-9 kills.

Someone else experiencing this?

Edited by Roadbuster, 14 August 2013 - 08:06 AM.

[627]

If i'm legged and in the reds, infront of my enemy, i smash that override button like hell and give out alpha after alpha.

I'm dead anyway so why not do as much damage as possible? Side effect is death by overheating and no one gets the kill, that's right.



Btw if you trigger an ammo explosion that kills the enemy, you get the kill.

Edited by 627, 14 August 2013 - 05:34 AM.

[Orion ji]

I had this happen ~3 times yesterday. Only time(s) it's ever happened. I'm running along at 80-100% and BAM dead. 2 games later I see someone (accidentally ?) paste folder nav to an include file and autoaim.exe....go figure.

[WarRats]

Yesterday... I was firing machineguns in a non-overheated state on a cold map standing in water. I killed a mech with my 2 machinguns and then... BOOM... it said I killed myself as soon as the other mech died.

[Kunae]

WarRats, on 14 August 2013 - 05:44 AM, said:

Yesterday... I was firing machineguns in a non-overheated state on a cold map standing in water. I killed a mech with my 2 machinguns and then... BOOM... it said I killed myself as soon as the other mech died.

Out of bounds.

[CarpetShark]

I had it happen to me a few days ago too. River City, in the river, in my Hunchback 4P. Not overheated, not out of bounds, no ammo to explode unexpectedly. One moment, I'm zapping enemies with my large lasers. The next: CarpetShark has been killed by CarpetShark.

I'll pay more attention now that I know it's not just a fluke.

[El Bandito]

CarpetShark, on 14 August 2013 - 06:18 AM, said:

I had it happen to me a few days ago too. River City, in the river, in my Hunchback 4P. Not overheated, not out of bounds, no ammo to explode unexpectedly. One moment, I'm zapping enemies with my large lasers. The next: CarpetShark has been killed by CarpetShark. I'll pay more attention now that I know it's not just a fluke.

Ok, counting the Missile tube abuse, this last patch is seriously borked up. And the game will launch in September?

[Dimento Graven]

El Bandito, on 14 August 2013 - 06:21 AM, said:

Ok, counting the Missile tube abuse, this last patch is seriously borked up. And the game will launch in September?

Anyone got any vids of this happening? I don't think it's that common myself. I've never just 'up and blowed up' without reason, for example, out of bounds as mentioned earlier.

I would hazard that there are still maps with incorrectly marked 'out of bounds' markers and if you're relatively close to an edge you're risking being out of bounds but not looking like you're out of bounds when you look at the mini or tactical maps...

[Gallowglas]

I've never experienced this personally. I mean, I've seen people kill themselves, but I've never blown myself up without knowing precisely why it happened.

Edited by Gallowglas, 14 August 2013 - 07:46 AM.

[Roadbuster]

Sry don't have any vids.
The best example I can give was a match on River City.
Some mechs were trying to gather in the tunnel under the base in upper city.
I dropped down and had a Jenner with its back turned to me about 50m away.
Hit it with an alpha strike of AC20, 3 SRM4 and 2 ML and its core went orange (yay hit registration).
After ~1-2 seconds (before I could fire again) it just exploded with the message that the mech killed itself.
No other teammate was near and the other mechs down there just noticed me a moment before the Jenner blew up.
The Jenner didn't fire a single weapon.



Out of the 2 mechs I killed in that match, I got 1 kill and the total kill count also missed that 1 mech.

Well, at least I'm not the only one who experienced this.

627, on 14 August 2013 - 05:32 AM, said:

Btw if you trigger an ammo explosion that kills the enemy, you get the kill.

Well, then I don't have any clue what happened.

Edited by Roadbuster, 14 August 2013 - 08:05 AM.

[Gallowglas]

Roadbuster, on 14 August 2013 - 08:02 AM, said:

Sry don't have any vids.
The best example I can give was a match on River City.
Some mechs were trying to gather in the tunnel under the base in upper city.
I dropped down and had a Jenner with its back turned to me about 50m away.
Hit it with an alpha strike of AC20, 3 SRM4 and 2 ML and its core went orange (yay hit registration).
After ~1-2 seconds (before I could fire again) it just exploded with the message that the mech killed itself.
No other teammate was near and the other mechs down there just noticed me a moment before the Jenner blew up.
The Jenner didn't fire a single weapon.

I wonder if perhaps this wasn't some buggy side-effect of HSR in which the server reconciled that the Jenner should have taken some extra damage...enough to kill him...but couldn't reconcile that the damage came from you? I don't know...just guessing. I really don't know.

[Dimento Graven]

Gallowglas, on 14 August 2013 - 08:08 AM, said:

I wonder if perhaps this wasn't some buggy side-effect of HSR in which the server reconciled that the Jenner should have taken some extra damage...enough to kill him...but couldn't reconcile that the damage came from you? I don't know...just guessing. I really don't know.

I know that since HSR there's been A LOT of kills that I made that went to other players, and some visa versa.

I'll be sitting there duking it out with someone, a team mate, happens by takes an opportunistic pot shot and keeps on going, I see my team mate's back to me, and I make a shot, the enemy blows up, and the game reports my team mate got the kill.

Like-wise, I've received a few kills I was NO WHERE NEAR and hadn't fire at for at least 2 or 3 seconds, and then I got the kill.

HSR, or something else on the MWO servers, is malfing kill detections.

But I ain't never blowed up for no reason neither...

Edited by Dimento Graven, 14 August 2013 - 08:17 AM.

[Roadbuster]

Gallowglas, on 14 August 2013 - 08:08 AM, said:

I wonder if perhaps this wasn't some buggy side-effect of HSR in which the server reconciled that the Jenner should have taken some extra damage...enough to kill him...but couldn't reconcile that the damage came from you? I don't know...just guessing. I really don't know.

Could be possible. HSR is pretty messed up anyway, at least for me (EU).
I'm just glad it's not a common thing.

[Wired]

People who are legged will start jumpjetting up to smash their other leg out.

[Asakara]

I saw a bug like that in CB. It happened to me a couple times.

For example, once on Forest Colony, in the middle of the map in a Jenner about a minute or so into the match I fired 4 medium lasers into an awesome and I immediately blew up. It was the second 4 ML alpha I fired in the game so I was around 1/3rd heat. I had yellow or untouched armor on all locations. Just BAM! Asakara has killed Asakara.

I had hoped it had gone away for good.

[Joseph Mallan]

Roadbuster, on 14 August 2013 - 05:25 AM, said:

Did someone else notice mechs just blowing up without giving the attacker the kill lately?
I've seen (when spectating) and had it happen (when killing a mech myself) a number of times in the last few days.
Seems like these pilots put ammunition in their CT to die from ammo explosion.
Do deaths through ammo explosion not count as kills for the attacker?

The times I've seen that happen none of the mechs had enough time to build enough heat to die from overheating, but the attacker didn't fire the killing shot either.
So, I guess what's happening is an ammo explosion.
Some matches ended with 12 mechs destroyed but only 8-9 kills.

Someone else experiencing this?

Not since closed Beta.

[o8oo Anarch]

I had a match a few months back on River City assault were I headed strait up and climbed the hill, headed (past where the capture point would be on conquest) across to the two tall buildings before the little open area between the city and the hill. Then my not so little Treb dropped dead.

The death screen said I'd killed myself with engine destruction, All my armour showed to be intacted but my CT was cored.

Only ever happened the once. My team and I had a good laugh about it and then I put it down to a glitch and moved on.

[Lorcan Lladd]

I admit it.
Sometimes I forget that 'Mechs now take damage from overheating at 100% capacity instead of 120% like it used to be, and I still haven't unlearned the habit to override shutdown during fights; as a result, I've been blowing up my own Jenner like it was my first time playing.

This could be one of the causes.

As for delayed kills - it's possible you have triggered a cross-section ammo explosion - it can take up to one full second or more for the explosions to reach and destroy a vital component and give you credit for the kill.
In the middle of a fight it can be hard to tell whether you've triggered such an event or received undue credit for a team mate's kill, especially if you're both focusing fire on the same target, but it certainly does happen.

Instant kills sometime occur with a bad roll for the localized random heat damage which is dealt to internals when overheating; if the damage is dealt to the cockpit or even the center torso of a very light 'Mech, instant death happens.
That said, I have seen a high number of players disconnecting or committing suicide lately.

The former is probably caused by bugs as usual.

Edited by Lorcan Lladd, 14 August 2013 - 08:39 PM.

[CarpetShark]

Lorcan Lladd, on 14 August 2013 - 08:29 PM, said:

As for delayed kills - it's possible you have triggered a cross-section ammo explosion

I would just like to reiterate that it happened to my Hunchback 4P. There was no ammo on board.

[Lorcan Lladd]

CarpetShark, on 14 August 2013 - 09:55 PM, said:

I would just like to reiterate that it happened to my Hunchback 4P. There was no ammo on board.

Hm.
Well, I recall something like that also happening to me exactly once during CB, but was months ago - I never found out what caused it, nor have I seen it happen again.