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.

Fuegan has a special rule where whenever he suffers an unsaved wound, he gains +1 strength and attack for the rest of the game. My question is, does this mean it's simply any wound you did not save against, and therefore you would still gain +1S/A even if you ignored the wound due to Feel No Pain?

Right now, I was thinking I'd run him with a Warlock council and/or Spiritseer in the hopes to roll the Eldar psychic power that can restores lost wounds. Just wondering if passing Feel No Pains also allowed him to hulk out.

SRSFACE wrote:
Fuegan has a special rule where whenever he suffers an unsaved wound, he gains +1 strength and attack for the rest of the game. My question is, does this mean it's simply any wound you did not save against, and therefore you would still gain +1S/A even if you ignored the wound due to Feel No Pain?

Right now, I was thinking I'd run him with a Warlock council and/or Spiritseer in the hopes to roll the Eldar psychic power that can restores lost wounds. Just wondering if passing Feel No Pains also allowed him to hulk out.

If he gets hit with a AP 2 attack and takes a wound he gets +1, FNP is specifically not a save.

Feel No Pain makes the wound count as being saved so no you wouldn't get +1S

There was some debate over the 'timing' involved with Feel No Pain not that long ago, and sadly the only conclusion I could see coming from it was 'The timing is broken.' Some of the Special Rules will have unusual conclusions if you apply the ideal that Feel No Pain does not prevent these rules from triggering, such as the Special Rule in the spot light right now. Other Special Rule and circumstances will come to their own unusual conclusions if you hold the mentality that Feel No Pain allows you to prevent the unsaved wound from triggering Special Rules. The most noticeable I remember being the ability to undo a model being removed as a casualty due to a failed Force Weapon activation.

Therefore it depends completely on which Special Rule, triggering on an 'Unsaved Wound,' is being discussed as to what outcome this board will provide as the 'correct one.'

 CrownAxe wrote:
Feel No Pain makes the wound count as being saved so no you wouldn't get +1S

Not quite.

FNP Makes the unsaved wound never happen.


The timing on this one is the end of the phase. By the end of the phase Fuegan has not suffered any unsaved wounds

So does that mean if a Dark Eldar Archon fails his Shadowfield but passes his FnP does his Shadowfield 'regrow' because it would be treated as if it never failed the save in the first place?

 ALEXisAWESOME wrote:
So does that mean if a Dark Eldar Archon fails his Shadowfield but passes his FnP does his Shadowfield 'regrow' because it would be treated as if it never failed the save in the first place?

Absolutely not.

He absolutely failed the save(otherwise FnP would not take effect), the unsaved wound is just removed.

JinxDragon wrote:
The most noticeable I remember being the ability to undo a model being removed as a casualty due to a failed Force Weapon activation.

Wait, what? Why would the model no longer be removed as a casualty due to a failed force weapon activation? I'm confused how that even came to be an issue.

It's my understanding that the interaction between FNP and Force Weapons is that triggering Force successfully means they can't take any FNP rolls as you cannot FNP against things with Instant Death. It comes into play when you run into the occasional model with both FNP and Eternal Warrior.

@KommisarKel: I don't have my Eldar book on me at the moment, but does it specifically say "At the end of any phase in which Fuegan suffers an unsaved wound" or simply "Whenever Fuegan suffers an unsaved wound"? Rules as worded there would then bring triggers into play.
Also does FNP specifically state that it counts as if the wound was saved against, or that it was ignored?

SRSFACE wrote:

JinxDragon wrote:
The most noticeable I remember being the ability to undo a model being removed as a casualty due to a failed Force Weapon activation.

Wait, what? Why would the model no longer be removed as a casualty due to a failed force weapon activation? I'm confused how that even came to be an issue.

It's my understanding that the interaction between FNP and Force Weapons is that triggering Force successfully means they can't take any FNP rolls as you cannot FNP against things with Instant Death. It comes into play when you run into the occasional model with both FNP and Eternal Warrior.

FNP and Force has actually been FAQd, you can never FNP a force weapon now, but in the past there were arguments about whether you can or not because the ID only occurs when the weapon is activated so it was possible to retroactively break the FNP rule.

@KommisarKel: I don't have my Eldar book on me at the moment, but does it specifically say "At the end of any phase in which Fuegan suffers an unsaved wound" or simply "Whenever Fuegan suffers an unsaved wound"? Rules as worded there would then bring triggers into play.
Also does FNP specifically state that it counts as if the wound was saved against, or that it was ignored?

Yes, it is specifically "At the end of any phase in which Feugan suffers one or more unsaved wounds" That is exact quote BTW.

FNP "Discounts the unsaved wound- treat it as being saved."

 Kommissar Kel wrote:

 ALEXisAWESOME wrote:
So does that mean if a Dark Eldar Archon fails his Shadowfield but passes his FnP does his Shadowfield 'regrow' because it would be treated as if it never failed the save in the first place?

Absolutely not.

He absolutely failed the save(otherwise FnP would not take effect), the unsaved wound is just removed.

But if the FnP is passed then you treat the wound as being saved. Wouldn't that mean treat it like he didn't fail his save in the first place?

I knew you were going to ask this.

No he still absolutely failed his 2+ save, thus triggering the shields failure.

He then makes his FnP counting the previously unsaved wound as now saved, but the shadow field had still failed(it was not what saved the wound).

There are 2 separate triggers here:
1)failing the save
and
2) Suffering an unsaved would
those triggers are distinct

SRSFace,
It rests completely on the words 'treat as having been saved' and the ideal that this means treating it as 'save successful' from the Saving Throw step forward. With such an outlook on the rule, it becomes possible for certain things to be undone simply because of the Feel No Pain result. This is because the timing involved would still allow for special rules to trigger before Feel No Pain, without denying Feel No Pain from triggering, so this leads to situations where we must 'undo' these results because the trigger no longer exists.

One of the things that would be undone is any perils caused by a Failed Force activation Roll, as they require an unsaved wound to begin with....

As before mentioned, not really my mentality on it, but I do see where they are coming from. We have Instructions, telling us to treat something as if it had been saved, which does suggest to me that it is unreasonable for something which triggers off an unsaved state to still function. That, by allowing it to trigger still, we are not treated it as having been saved and therefore violating Feel No Pain's instructions. Like wise, this side of the argument has their own list of Special Rules which cause unusual circumstances if you do not deny them the trigger, so precedent is not the strongest on either side.

Therefore, it will always have to be case by case for me.

Feel no Pain is not a saving throw.... (???)

No, it is just a Special Rule, which is very useful as it is allowed in situations normal Save are not.