Issue: If a Necron Night Scythe suffers a “Wrecked” or “Explodes” result, do the embarked models suffer S10 hits from the Crash and Burn rule?

Holding: No, models embarked on a destroyed Necron Night Scythe are placed into reserve without suffering any further ill effects.

Justicar GiantKiller delivers the opinion of the court.

This issue arises from the unique special rules of the Necron Night Scythe transport, which tell us that a destroyed Night Scythe’s passengers do not disembark as normal, but are placed in reserve instead. See Codex: Necrons p. 51  The question arises, then, as to whether or not models embarked on a Night Scythe (which can only zoom due to being Supersonic) suffer S10 armor-ignoring hits as indicated in the Crash and Burn Rule (BGB p. 81) when the Night Scythe is wrecked or explodes.  We’ve received quite a few emails on this subject since 6th edition was released.  We’ve read a number of arguments on both sides of the issue and have been arguing it amongst ourselves for some time now.  We were hoping this issue would be addressed in the 6th Edition Necron FAQ, but it wasn’t, so we’ve set about constructing our opinion.

As always, we begin our analysis with a thorough reading of the relevant rules.

The Night Scythe’s rule tells us:

“If the Night Scythe is destroyed, the embarked unit is not allowed to disembark, but instead enters reserve (when they arrive, they cannot Deep Strike)” Codex: Necrons p. 51

In 6th Edition, the Night Scythe is both a flyer and a transport, and it cannot hover, so we look to the Crash and Burn rule for flyers to find out what happens to passengers when a flying transport is destroyed while zooming:

“If a Zooming Flyer is Wrecked or Explodes, its flaming debris rains down on the battlefield.  Centre the large blast marker over the Flyer – it then scatters 2D6″.  Any model under the blast marker’s final position suffers a Strength 6, AP – hit.  The Flyer is then taken off the board.  If the Flyer is also a Transport, any models within suffer a Strength 10 hit with no armour saves allowed.  Survivors are placed anywhere within 3″ of the blast marker’s final position and in unit coherency.  Any models that cannot be placed are removed as casualties.” 6th Edition BGB p. 81

So to use some complex legal jargon, it’s ouch time for the passengers of a crashing zooming flyer.  Breaking this down into an order of operations, the Crash and Burn rule instructs us to:

1. Scatter the blast and resolve hits against models it touches.

2. Remove the Flyer.

3. Resolve what we’ll call ‘Crash and Burn Hits’ against embarked models.

4. Place survivors.

5. Remove as casualties any models that can’t be placed.

We note that the rule does not use the terms “Destroyed” or “Disembark”.   Some have argued that since the Crash and Burn rule never uses these terms, as referenced in the Night Scythe’s rule, that the Night Scythe’s rule no longer applies in 6th edition.  We find this argument unpersuasive as it is in clear violation of the Superfluous Language Canon and the Use Context Canon.  Not only would such an interpretation render the language of the Night Scythe’s rule ineffectual, but it would completely ignore the appropriate context.  Interpreting the Night Scythe’s rule in light of 6th edition and the Crash and Burn rule in particular, it is clear that it is describing rules for passengers getting out of a broken flyer.  This is precisely the situation contemplated by the Crash and Burn rule.  We would have a hard time arguing with a straight face that a wrecked or exploded Night Scythe wasn’t destroyed, and that its passengers aren’t attempting to disembark.

Some have argued that pursuant to the Necrons’ fluff, the models embarked on a Night Scythe are not actually “on” the Night Scythe, but are instead lying in wait somewhere else to be transported into the battle via Invasion Beams.  They would therefore be immune to the effects of being aboard a crashing flyer because they weren’t on board when it crashed.  We find this argument entirely unpersuasive as fluff has no bearing whatsoever on the interpretation of the rules as written.  We note that other rules also refer to Necron passengers on a Necron Night Scythe as embarked models, just like they would for any other race’s passengers.  (See “invasion beams” Necron FAQ, 6th Edition, v1.1 p.2).  Transported Necrons are indeed embarked models and they therefore follow the rules for embarked models, regardless of their fluff.  Simply put, fluff isn’t rules.

Our reading of the rules thus far suggests that the Night Scythe’s rule does apply in the situation where a Night Scythe is wrecked or exploded, and that it conflicts with the Crash and Burn rule.  Crash and burn tells us to resolve hits, place the surviving models on the board, then remove any that can’t be placed as casualties.  The Night Scythe’s rule, on the other hand, forbids us from placing the models on the board, instructing us to place the entire unit into reserve instead.

Since these two rules are certainly in conflict, we turn to the “Basic versus Advanced” rule for guidance on how to resolve the conflict:

“On rare occasions, a conflict will arise between a rule in this rulebook, and one printed in a codex.  Where this occurs, the rule printed in the codex always takes precedence.” 6th Edition BGB p. 7

This is GW’s way of articulating the Specific > General canon, which has been a mainstay of 40k rules interpretation since, well, forever.  So where these rules conflict, the Night Scythe’s rule wins out.

But where do they conflict?  It is important to note that the more specific rule overrides only the portion of the general rule it contradicts.  We may take out only as much as is necessary to resolve the conflict.  It has been argued, therefore, that the Night Scythe rule only overrides #4 from our order of operations above – the “place survivors” portion.  By that interpretation, the unit would still suffer the ‘Crash and Burn hits’ at step #3, then be placed into reserve on step #4 pursuant to the Night Scythe rule.

However, such a narrow interpretation would create further conflict with #5 from our order of operations – remove models which cannot be placed. The last sentence of the Crash and Burn rule tells us “Any models that cannot be placed are removed as casualties.”  If the unit is placed into reserve, none of the models, even the surviving ones, can be placed according to the Night Scythe’s rule.  Therefore, the entire unit would be destroyed every time.  That’s clearly not the drafters’ intent, and it would render the Night Scythe rule pointless, so we’d have to ignore that last sentence of Crash and Burn, too.   But we ultimately find even that interpretation to be too narrow in light of the language of the rule itself, and in light of context.

The language of the Night Scythe’s rule provides us with some guidance as to where to start ‘cutting’ language.  The language of that rule “if the Night Scythe is destroyed” tells us it is triggered upon the destruction of the Night Scythe itself.  We concede that the Crash and Burn rule does not use the word “destroyed”, but as we’ve suggested before, it is clear to us that once the Night Scythe is removed from play, it’s destroyed.  That removal from play occurs at step #2 in our order of operations above – remove the flyer.  This strongly suggests that it is immediately after #2 where the Night Scythe’s own special rule ‘takes over’ and dictates the rest of the order of operations, which would mean the unit is simply placed into reserve without suffering any further ill effects.  But simple use of context provides a stronger argument still.

Again analyzing the language of the rules in light of context as mandated by the Use Context Canon, there is a compelling argument to be made that the Night Scythe’s go into reserves rule replaces the entirety of what we’ll call the ‘getting out process‘ for Necron models embarked on a destroyed Night Scythe.  This getting out process is the sequence of rules we follow to decide what happens to a unit inside a newly destroyed transport.  While the specifics of each getting out process depend on the type of transport and the manner of its destruction, there are key similarities throughout.  Reading the Crash and Burn rule in light of the context provided by the “Effect of damage on passengers” rules on BGB p. 80 (the most similar rules to Crash and Burn), we conclude that resolving hits against embarked models is simply a part of the getting out process when a transport vehicle is well and truly destroyed.  The getting out process includes resolving hits against embarked models, placing the models, and removing the models which cannot be placed.  The Night Scythe’s rule therefore overrides all of those portions of the Crash and Burn rule.  We find this argument the most persuasive.

With that portion of the Crash and Burn rule thus overridden by the Night Scythe’s rule, our inquiry is resolved.  Models embarked aboard a Zooming Night Scythe which is destroyed do not suffer ‘Crash and Burn hits’, are not placed on the board, and are not removed if they cannot be placed.  The unit is simply placed into reserve.

So holds the court.




Disclaimer – the picture of yummy, yummy night scythes used above is not our work and no challenge to the creator’s IP rights is intended.

10 Responses to “Rulings – 6th Edition Necron Night Scythes, Crash and Burn, and Embarked Models”

  1. As logical a conclusion as any. :)

    I find a simple approach to this issue (and many others to be)

    Step #1) First prove that it is NOT clear RaW that any assertion is correct. (This is very easy to do with this issue as you pointed out, noting that the Necron’s Night Scythe rules demonstrate no discernible “time” element, an element which MUST be assumed in order for the S10 AP 1 hits to be argued as applicable.)

    Step #2) Once it is proven that the rules prove nothing, let context (ochom’s razor) make the final decision.

    What I would suggest though is that you add another Canon which you are missing. Although you state that “Fluff does not make a rules argument”, there should be some principle against making an argument whilst willfully ignoring the obvious, no? :)

  2. I agree that “willfully ignoring the obvious” is a terrible idea when interpreting rules. Put another way, it is incredibly important to use your common sense when interpreting rules language. But I don’t think we’re missing a canon here. Common sense is a concept that is already reflected in several of our canons.

    Check out:
    The Use Context Canon
    The Drafters Intent Canon
    The Occam’s Razor Canon
    The Absurdidty and Injustice Canon

    …and note the actual Supreme Court language we used to derive these rules – it’s quoted on those pages. I think you’ll find all of those canons of interpretation mandate the use of common sense in rules interpretation.

    Hope this helps!

  3. Awesome. What you should have said is “why don’t you read all of our Canons first, dumbass?” lolz :) The Absurdity and Injustice Canon covers the point very clearly. :)

  4. Your argument doesn’t take into account the scope of “Effects of damage on passengers”, despite referencing it. Any vehicle that suffers a “stunned” or “shaken” result is unable to fire weapons. This is passed on to embarked units being unable to fire weapons, and units which disembark are still unable to fire weapons. This proves that units CAN be affected by damage to the transport vehicle, even while being transported.

    This would imply, then, that the only part involved in the “getting out process” as you put it would be the actual placing of models on the table after determining where you are allowed to place them. Since this happens after the Crash and Burn rule would cause damage to the embarked unit, they still suffer damage as normal despite the replacement to the “getting out process”.

  5. Thanks for your argument, Dan!

    I agree with you that passengers can be affected by damage to a vehicle. Not every unpleasant thing that can happen to a passenger is part of the “getting out process” we’re dicussing.

    The crash and burn wounds at issue here are part of that process.

    The inability to fire as a result of a shaken vehicle isn’t.

    See the difference?


  6. I don’t think there IS a difference, to be honest.

    “Effects of damage on passengers” passes along an effect (unable to shoot) to the embarked units, whether they disembark or not. Where the unit is, or ends up, is irrelevant. The same process is involved in the “Crash and burn” mechanic.

    Where the models finally end up, either on the table (disembarked) or in reserve (Night Scythe rules replacing “disembarking”) is irrelevant to them being exposed to the effects of the vehicle suffering a Crash and burn result first.

    Your initial assessment of the process involved is correct, but your evaluation afterwards is suspect.

    1. Scatter the blast and resolve hits against models it touches.
    No arguments here.

    2. Remove the Flyer.
    No arguments here.

    3. Resolve what we’ll call ‘Crash and Burn Hits’ against embarked models.
    Happens as instructed.

    4. Place survivors.
    Place survivors into reserve, instead of on the table, as per Night Scythe rules.

    Remove as casualties any models that can’t be placed.
    Luckily, all survivors are already “placed” into reserve, so they are safe from this clause in this instance.

    The Night Scythe rule, currently, only changes “disembarking”, not anything or everything that happens before they attempt to actually leave the vehicle.

    Your own “superfluous language canon” tells you not to ignore parts or a rule in the application of other parts of the same rule, and as I have demonstrated here, every part of both rules is applied equally.

  7. Dan, while your argument is well taken, I disagree.

    Resolving the crash and burn hits, placing survivors, and killinng off any that can’t be placed are all part of the getting out process which is overruled by the night scythe’s rule.

    Your argument that some damage effects affect passengers without forcing them to disembark does not support the conclusion that all effects on passengers must be separate from the getting out process.

    This ruling doesn’t violate the superfluous language canon, as no language is being rendered superfluous. Being overridden in this instance by the night scythe’s rule does not make any of the crash and burn rule superfluous. You may have a stronger argument based on the read rules together canon. But we’ve considered that and nevertheless came to the decision posted here.

    Also, i’d argue that entering reserve does not count as being placed so as to avoid destruction by the last line of crash and burn there.


  8. I would have to agree with Dan, Being placed in reserve would count as being place, thus leaving them damaged but able to enter reserve by any other available means.

    The Necrons are placed in step 4, and since no models cannot be placed are not effected by step 5. I feel the main confusion is in steps 2-3 which really step 3 happens at the same time as step 2.

  9. Well, looks like my post was badly timed. They officially follow this ruling now….

  10. @Charlotte, just because they faq’ed it doesn’t mean it wasn’t worth arguing about. This is all about the fun to be had in detail-oriented dissection of awkwardly-written rules.

    My issue with your argument is that I don’t agree with your assertion that being placed in reserve counting as being placed in the context it’s being used in the rule.

    In case anyone’s wondering, the FAQ ruling Charlotte’s talking about is this one, which addresses the issue in this article:

    “Q: If a unit is embarked on a Night Scythe that is Wrecked or Explodes, do they suffer Strength 10 hits with no armour saves as per the Crash and Burn rules before they are placed in reserve? (p81)
    A: No.”
    -Codex: Necrons FAQ v1.2, January 2013


Leave a Reply



You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

© 2009-2011 The Rules Lawyers Suffusion theme by Sayontan Sinha