Bastiladon and now Leviadon variable saves

[azdimy]

How do you roll your saves if you take enough wounds that your save could have different values as a result of an attack?

Do you roll all your saves at once and are considered to be at the save you have at the beginning of the attack. So if the monster take 10 wounds. Roll 10 dice and save at you top braket save value if your monster had no wound on it?

Or do you roll dice separately as in the same attack sequence the armor save changes? Roll 1 dice at a time or roll x  dice where x is the potential of ubsaved wounds that could change your save and then roll the next batch and so forth to save with the new save value

[Boar]

3 minutes ago, azdimy said:

Do you roll all your saves at once and are considered to be at the save you have at the beginning of the attack. So if the monster take 10 wounds. Roll 10 dice and save at you top braket save value if your monster had no wound on it?

This one, mechanically all unit's attacks are resolved and then damage is allocated to unit. If another unit attacks later, than that 2nd attacker could face different save profile.

*For purposes of damage negation you allocate wounds one at a time, sometimes it can be different here as f.ex. Throggoth can have artifact that stops working on roll of one, so that would be rolled one by one. But that's different problem

 

Edited November 12, 2020 by Boar

[NinthMusketeer]

When a unit shoots/fights, it resolves all of its weapon rolls including saves. Only after all of the attacks are resolved does damage allocation occur and at that point the save rolls have already been made. Such damage would be relevant to subsequent shoot/fight actions, however. To break it down:

-Hero A is armed with two different melee weapons and attacks a Leviadon. For the first weapon he rolls his hits and wounds, then the Leviadon rolls saves. Failed saves result in damage, which is tallied but not yet allocated.

-Hero A then does his hits and wounds for the second weapon, followed by saves, and additional damage is added to the tally.

-Hero A has now made all of his attacks, and so the damage is allocated to the Leviadon. This is when rolls to negate damage would occur, if such a rule were in play.

-Unit B now attacks. The damage from Hero A has been allocated, so any changes to the Leviadon's save characteristic will apply when resolving the attacks of Unit B.

A sidenote is that this makes the order in which multiple units attack a Leviadon quite important.