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.

If Lucius is MSS'ed in a challenge and manages an invulnerable save against his Power Sword

Does he then have to cause an AoSS wound on himself

That can then trigger invulnerable save in order to strike again until he is hit by his own armour.

Can this happen or am I reading it wrong.

Omg madness, *head explodes*

RAW yes but...

RAW he takes the wounds. Should it get faqed otherwise? Absolutely. Until then either housrule or don't let Lucious near MS scarabs...

Could this theoretically become an infinite loop? As each wound generated by AoSS is a brand new wound?
Or rather it's just a guaranteed wound as you'll eventually fail the roll.

The Str 4 AP 2 hit may fail to wound so it's not an automatic wound nor an infinite loop.

Take it one step further. Two chaos armies collide and Lucius is fighting Lucius.

Lucius A does a wound to Lucius B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B makes the save and does a wound back to A.
A makes the save and does a wound back to B.
B finally fails his save.

copper.talos wrote:
The Str 4 AP 2 hit may fail to wound so it's not an automatic wound nor an infinite loop.

True, sorry I'd forgotten it was an S4 hit rather then a wound.

Interesting. We often have contradictions that cause the rules to lock, but I've never encountered an infinite loop before.

Facinating...

As already mentioned, it causes an automatic 'hit' but not necessarily a 'wound'. (Given it's strength 4 AP-2, it bypasses his armor and ignores cover, but would only wound him on a 4+)

That said, if Lucius keeps successfully wounding and passing his own invulnerable saves in this scenario? it looks like currently his own armor will continue to try and stab him until he either fails the save or fails to wound himself.

Indeed, its an interesting little quirk.

OP has caused a ripple effect in the rules. Grats OP.