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.

Hi,

Looking for some help on how to resolve a sitution. I had a quick look so apologies if the solution has been presented before.

There seems to be a conflict between wound pools (p34), combatant slain (p101) and D weapons (p163). The situation was as follows:

D-Thirster (D-Axe) in a challenge with a Necron Overlord (3++) in the middle of a larger combat. Overlord took off a single wound from the demon then demon made four hits on Overlord at I1. These were rolled as a 1, 3, 4, 6 (so dead either way). Ignoring the 1, the rolls were D3: 1, D3: 3, D6:6 for a total of 16 wounds (1+3+6+6).

What happens now? I suggestd that I could take the wounds in order, so I could take up to 4 invulnerable saves vs the wounds generated via the D3s. I saved three of them, so the overlord took 13 wounds. To which Op tried using the combatant slain rule to re-allocate these 13 hits (12 of them no save allowed whatsoever, not even invulnerable) to the rest of the squad. I said that the D weapon rul directly contradicts that and multiple wounds "generated" are lost.

There are a few things that stand out / I want clarity on:
1) every wound on the DWAT is 'generated' by rolling what do we do here? There is no 'initial' wound so is every D 'wound' a multiple?
2) there doesn't seem to be a thing as 'D' wounds, so how does this work with re-allocation, wound pool and saves etc?
3) what should have happened? I suggested rolling one at a time, to see if the Overlord was dead, if he was, then the remaining D hits are transfered, but this isn't what wound allocation says (you allocate wounds, not hits) but does allow you to ignore additional wound generated.
4) Invulnerable saves can be taken against D hits (unless a 6 is rolled) - does one invulnerable save roll save from D3 Wounds or just 1?

Help! Thanks,

Okay so the way this works is. All hit rolled then roll wounds 1 at a time. So that the d3 wounds generated can be taken rolled to try to be saved by the overlord. The first d3 are taken on the overlord and rolled to save. Then if he is still alive he takes the next d3 hit and rolls to save those. And so on. If he dies 1 other model in the unit takes the D hit. D hits cause only 1 model to be damaged. So I hit an ork boy and roll a 6 on the D table. 1 ork loses 6 + d6 wounds not 6 + d6 orks die.

I hope this helps. Fyi I had no chance to proofread so I hope I typed this up clear enough.

mhalko1 wrote:
Okay so the way this works is. All hit rolled then roll wounds 1 at a time. So that the d3 wounds generated can be taken rolled to try to be saved by the overlord. The first d3 are taken on the overlord and rolled to save. Then if he is still alive he takes the next d3 hit and rolls to save those. And so on. If he dies 1 other model in the unit takes the D hit. D hits cause only 1 model to be damaged. So I hit an ork boy and roll a 6 on the D table. 1 ork loses 6 + d6 wounds not 6 + d6 orks die.

I hope this helps. Fyi I had no chance to proofread so I hope I typed this up clear enough.

Thank you!

This is what I thought... but op disagress and says Wound Pool rules etc mean it doesn't work like that (ie generation of wound pools, allocation of wounds, nothing about reallocating hits etc).

Yeah the D tables causes that many wounds to the single model that takes the hit. Just as if it were a vehicle - it's 1 pen hit that causes it to lose ...so many hp.

mhalko1 wrote:
Yeah the D tables causes that many wounds to the single model that takes the hit. Just as if it were a vehicle - it's 1 pen hit that causes it to lose ...so many hp.

Thank you again!

I guess the challenge back is this: where in the rule book does it allow a hit to be reallocated (as opposed to a wound)?

It is a wound that causes d3 wounds instead of one. It is still only a single wound allocated from the pool.

You also roll one save against all d3 , and you cannot kill more than one model per destroyer hit (multiples after allocation, no allowance to reallocate "excess" wounds )

nosferatu1001 wrote:
It is a wound that causes d3 wounds instead of one. It is still only a single wound allocated from the pool.

Destroyer weapons don't roll To Wound though.

If the attack hits, roll on the table above instead of rolling To Wound or for armour penetration.

True, it's just trying to make a poorly written rule make sense. There is still no way to allocate the d3 wounds eg 3 to more than a single model.

 Ghaz wrote:

nosferatu1001 wrote:
It is a wound that causes d3 wounds instead of one. It is still only a single wound allocated from the pool.

Destroyer weapons don't roll To Wound though.

If the attack hits, roll on the table above instead of rolling To Wound or for armour penetration.

Right, this chart replaces the To Wound roll with something else and does not tell you to allocate these Hits like a Wound Pool.

Closest thing I have is that something happens on a 2+ to the model and, "Multiple Wounds/Hull Points inflicted by a Destroyer hit do not carry over to other models in the unit (any excess are lost)."

Also keep in mind that the 2-6 results state they automatically Wound and the model loses X Wounds, not the unit.

Just to simplify things, I would treat Hit Allocation like Wound Allocation, much like Majority Armour Save in place of Majority Toughness for Gravitation Hits. The precedence is there and is the only asiest to use without reverting or making something up.

The problem is, you need to make up hit allocation or reallocation instead.

Raw the only way to play is that no D hits ever spill over. That's clearly not RAI however.

The way I would resolve them is sequentially, one "Destroyer Table Roll" at a time. So the D thirster gets four hits:

Roll once on the table: a 1, the overlord is fine.
Roll the second time: a 3, the overlord is required to take an invulnerable save and passes, avoiding d3 wounds.
Roll a 3rd time: a 5, the overlord is required to take an invulnerable save, fails it, then suffers d3 wounds that are Str 10 for the purposes of instant death, being slain.
The fourth roll spills out of the challenge (assuming hit allocation works like wound allocation where it is done one at a time) and rolls again on the D chart, this time against one of the Overlord's retinue, rolling a 6 and obliterating the poor Necron.