Forum adverts like this one are shown to any user who is not logged in. Join us by filling out a tiny 3 field form and you will get your own, free, dakka user account which gives a good range of benefits to you: No adverts like this in the forums anymore. Times and dates in your local timezone. Full tracking of what you have read so you can skip to your first unread post, easily see what has changed since you last logged in, and easily see what is new at a glance. Email notifications for threads you want to watch closely. Being a part of the oldest wargaming community on the net. If you are already a member then feel free to login now.

Question one: If i had a BattleWagon with boys and a Mek with KFF in it and my opponent explodes it, would my boys get the +5 save from the KFF?
Question two: If they were next to a vehicle as it explodes would they get the +5 save?

macace wrote:Question one: If i had a BattleWagon with boys and a Mek with KFF in it and my opponent explodes it, would my boys get the +5 save from the KFF?
Question two: If they were next to a vehicle as it explodes would they get the +5 save?

With the boys unit inside a vehicle that explodes, there is no question they would benefit from the KFF against the explosion result (because the rules specify those hits are 'treated just like hits from shooting').

With the boys sitting next to an exploding vehicle the rules don't specify one way or another whether cover saves are allowed (or even if those hits are resolved like shooting), so I can't give you a 100% answer. However, my default opinion is that since the rules for general casualty removal are found in the rules for the shooting phase, and they include the rules for cover saves, in general you DO get to take cover saves if at all reasonably possible. So I'd personally say that yes the KFF save is allowed against a nearby vehicle explosion, but you will get some people who disagree with that concept and the rules aren't clear one way or the other.

Why thank you kind sir. Much Appreciated!

I always wondered about the KKF and how it affected units while the mek is inside a vehicle. I played in a few Apocalypse games where someone had three stompas and three skullhammas. In each of the stompas there was a mek with a KFF. The player positioned the stompas 6 inches away from the skullhammas. Basically with 6 inches in between each unit and a mek in every other unit, the player had it where he had the save from the mek on each unit. Does it really work this way?

Lord Scythican wrote:I always wondered about the KKF and how it affected units while the mek is inside a vehicle. I played in a few Apocalypse games where someone had three stompas and three skullhammas. In each of the stompas there was a mek with a KFF. The player positioned the stompas 6 inches away from the skullhammas. Basically with 6 inches in between each unit and a mek in every other unit, the player had it where he had the save from the mek on each unit. Does it really work this way?

Yes. GW's Ork FAQ clearly states that when a Mek is onboard a vehicle (like everything else) you then measure range from the hull of the vehicle.

Which is why you bring S weapons, which ignore cover saves.

isn't the KFF a 4+ cover?

5+ cover to nonvehicles, 4+ cover to vehicles.

What happens if the Mek is inside vehicle 1, and vehicle 2 blows up - do the Boyz in vehicle 2 get coversaves if the hull of 1 is within 6"?

Yes, because the unit is within 6" according to the rules for Embarking.

A group of friends of mine say that you can't "target" units inside of a vehicle.

Otherwise, Doom would be able to target units inside a transport. The Tyranid FAQ states:

"Does the Doom of Malan’tai’s Spirit Leech ability
affect units embarked in transport vehicles?

A: No."

You are not targetting them, at all. It is not shooting, and the Dooms offensive ability is not relevant.

The rules for whether a unit is within range when embarked are very, very clear. Your friends may wish to houserule it, but that is their prerogative and does not make them the written rules.