Damage event flow changed?

[dark6161]

Event flow:

sapper got charge on my tiger

sap goes boom

I run away (obviously sap clipped or got misplaced)

no visual damage (white or brown smoke)

I keep running for about 4km (no smoke at any point as I kept checking back for sapper that was following me)

engine blows out

I start scanning (I was in the middle of nowhere by now)

2-3mins later tank explodes

Question is:

somethinhg changed in the damage event handling that I missed in the readme?

http://csr.wwiionline.com/scripts/services/persona/sortie.jsp;jsessionid=05943EBE31EF62C21C5EA6084382A33A?sid=2263630&pid=410440&page=1

mission attached as maybe the sapper can say if there was any smoke from my engine on his part after the sap

looking back it would have been smarter to just respawn as I was near monchen ab when the sap missed

so any info about this that might improve the decision making please share it

PS. the sapper got the kill so no 17pdr on the hill/6pdr in the bushes explanation works as there was no tracer/no sound happening

I kept scanning once I couldnt see the sapper following me (after the first 500m or so)

Edited April 1, 2011 by dark6161

[petie]

Have done this on a matty, maybe same here.

Shoot matty till smoke comes from engine area, keeps shooting till smoke dissapeares, matty drives for a few km and engine dies,(Shows loss of oil pressure in engine) which eventually if drive makes engine die.

maybe 17pder made the explode shot but as the engine was already dead the sapper was awarded the kill.

Same reason hear on chat that someone has flamed a tank and not got kill, someone else got a crit on either gunner, driver, engine or tracks

Edited April 1, 2011 by petie

[gervleth]

yes it's been happingto people on both sides.

[Hinfoos]

probably a brit grenadier lying in a bush 200meters away

[dark6161]

yes it's been happingto people on both sides.

I wasn't implying a side issue

just didn't pick up anything in the readmes

hinf00noob...hanghey'r is not here

[Hinfoos]

I wasn't implying a side issue

just didn't pick up anything in the readmes

hinf00noob...hanghey'r is not here

pah havent been flying for months im a squishie now

[chiefjr]

Ever since I think 1.33 if a vehicle's engine dies (or vehicle is on fire) the vehicle later blows up for whatever reason. It could be seconds, minutes, hours, not sure why this happens. Just from common observation - Jester

[kireh]

probably a brit grenadier lying in a bush 200meters away

You should not fire the British grenadier at distances less than 2 Km, dear god why are you folks wasting our wonder weapons ,. .

[bronco69]

its like with the 232 kill on a MATTY

• permanent brown smoke - fuel leak
  
• brown smoke gone - oil leak - 1 engine lost oil pressure - 1 engine will die within next few mins or 100-200m - 2nd engine cant "move" the tank alone - so tank will loose both engines - engines toast - hit ESC and tank goes booooom
  

thats why i keep firing with my 232 into the special spot on the MATTY until the brown smoke is gone. sure sign for a "soon" kill on the MATTY

[gvonpaul]

I've had the same thing happen in a Tiger and PIVG several times. It never explodes until I hit escape. Was wondering if it was just a coincidence, but apparently not.

[DOC]

With patch v1.31 release, any critical kill made on a vehicles engine (thus awarding a kill to the shooter and disabling the vehicle) will result in the vehcile blowing up on despawn, rather than just "blinking out".

Personally, I don't go for it but it was done because it looks cooler for those first experienceing the game to see stuff blow up on the battlefield.

So this is actually not a bug.