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.

So i couldnt find this in the search, but if a monolith deep strikes on top of enemy figures, and in an attempt to move out of the way, per the Necron codex, and the unit runs into more of his own units with no way of moving between, what happens?




lyy yy yy l
l x x x x xl
lx x x x x l
l............l
lz z z z z zl



Horrid picture I know, but say that the monolith deep strikes on the "x" (normal guardsman) but does not touch the y figures at all, the "l" are impassible terrain, and the "y"s are heavy weapons teams. The monolith takes up the space between x and z but still forces the x figures closest to z into the y figures. Now since these figures move through other friendly units what is the resolution?

There are really only two that I can see, either both x and y move, or x is destroyed and y stays where they are. Just curious as to how this would be played as this almost happened in a game played tonight.

s2

Edit: To keep the format of my horrible picture, I put .... in there to show that it was blank

gak hits the fan.

if the monolith hits terrain or units, as per my knowledge (unless a rule dictates otherwise) you've got a mishap test to do.

Captain Solon wrote:gak hits the fan.

if the monolith hits terrain or units, as per my knowledge (unless a rule dictates otherwise) you've got a mishap test to do.

Nope, cause it has a special rule.

instead of moving the X models back into the Y models, move them left or right. There is no rule that says models that are under the monolith are destroyed if they cant move. So I would just move everything until the monolith can be placed.

Yes, the monolith has a special rule, saying that if it would be destroyed by landing on top of enemy models it instead pushes them out of the way.

However, you can only ever be destroyed by enemy models by rolling a destroyed result on the mishap table after scattering on top of enemy models.

DS a mono on top of enemy models and you have a 1/3 chance of pushing them away, and 2/3rds of delayed or misplaced.

move the Xxxxxx closest to the monolith first without their bases touching the bases of fiendly models from another unit the shortest possible route to get out from under the monolith.

Then repeat the process with the xxxxxx the farthest away fromt he monolith. bet you there will be a gap at least 1'' wide for your guys to all squeeze through

kill dem stunties wrote:Yes, the monolith has a special rule, saying that if it would be destroyed by landing on top of enemy models it instead pushes them out of the way.

However, you can only ever be destroyed by enemy models by rolling a destroyed result on the mishap table after scattering on top of enemy models.

DS a mono on top of enemy models and you have a 1/3 chance of pushing them away, and 2/3rds of delayed or misplaced.

I never thought of that one...but I can't find anything logically wrong with that interpretation.

It says to move the models out of the way. If they cannot move towards y becuase there is no room, then move towards z. If there is still no room then the rules do not cover what to do. It does not say you get to destroy the models. If you try to argue that they are destroyed, I would state that the models cannot be moved and your 'lith mishaps as you have no room to place it on the table. While neither are in the rules, both would be valid arguments. My suggestion would be to avoid this situation by not striking where you would have this issue.

I will have to go get my old 3rd ed rulebook but i believe its because back then scattering onto a unit = destroyed.

Now however you mishap and roll on a d3 table.

Hyperviper - I think thats what my group and I are going to have to do. Luckily it didnt happen as our group is fairly competitive when it comes to team games.

Kill Dem - You are right, but Necron's have a rule whereby Monoliths push enemy units out of the way before they land. I believe that buildings and other non-unit type board features still cause those mishaps though.

NEC.21C.03 – Q: Can a Monolith attempt to Deep Strike directly over enemy models? If it does end up landing within 1” of an enemy model does it still roll on the Deep Strike mishap table (just ignoring the „Terrible Accident!‟ result)?
A: It can attempt to land directly over an enemy model and if it does so, the enemy models are pushed out of the way as described in its „Deep Strike‟ rule and no mishap is rolled [clarification].
Ref: RB.95A.03, TYR.48E.01, TYR.51B.02

thats not a clarification. Thats a rules change and wasnt needed at all.

Inat is always "fixing" things how they believe they should work, its bunk.

The rule says its not destroyed by landing on models, too bad that only happens after a mishap. If you dont roll a mishap you cant legally proceed.

First let me say DS a Monolith is just silly, but Slightly off topic, One thing I always thought that should happen since when you do deepstrike you are considered moving at cruising speed it should cause a tank shock.

One of the guy I play uses necron and this has come up a couple times when playing in densely packed terrain.

We couldn't really come up with a good answer so we played it like unit X had to be pushed into unit Y and unit Y would in be pushed back far enough to accomodate them.

kill dem stunties wrote:thats not a clarification. Thats a rules change and wasnt needed at all.

Inat is always "fixing" things how they believe they should work, its bunk.

The rule says its not destroyed by landing on models, too bad that only happens after a mishap. If you dont roll a mishap you cant legally proceed.

The INAT ruling merely keeps the function of the Monolith's deepstriking special rule the same as it was when the codex first came out. It's the type of thing that should have been addressed by GW on their FAQ's, but falls under the heading of things too obvious for them to bother discussing.

And? thats completely irrelevant, if thats what they want thats fine, but list it as a rules change, not a clarification.

The rules say something different happens than what their faq says.

kill dem stunties wrote:And? thats completely irrelevant, if thats what they want thats fine, but list it as a rules change, not a clarification.

The rules say something different happens than what their faq says.

Does it really matter whether they call it "clarification," "rules change," or "marmalade?"

Seriously, at the end of the day, does the name they give it affect anything at all?

There are 4 cases that can cause a DS mishap.
Off Table
Impassable terrain
Friendly models
Enemy models

Assuming that the only thing in the way is enemy models, you go by what the Necron Codex says...move the enemy models out of the way.

You don't roll for a mishap. How you handle moving the enemy models is up for discussion.

njfed wrote:You don't roll for a mishap.

Why wouldn't you roll? You're not destroyed by landing on enemy models unless you get 1-2 on the d6 roll - and that's all the monolith's DS rule helps against.

Spetulhu wrote:

njfed wrote:You don't roll for a mishap.

Why wouldn't you roll? You're not destroyed by landing on enemy models unless you get 1-2 on the d6 roll - and that's all the monolith's DS rule helps against.

Long, long ago in a edition long forgotten, the Monolith's DS rule made perfect sense. That was 2 edition of 40K ago. The intent of the rule was that the Monolith could never mishap when deep striking onto enemy models. Then the DS rules got completely redone, so you have to go with what the original rule intended. At least, that is the way it is played in official tournaments...you and your friends can house rule the Monolith to roll on the mishap table if you want.

Spet and Kill Dem have an pretty good RAW argument.

The only time a monolith's special rule would kick in is if it rolls a destroyed result on the mishap table.

Yes the sheer mass prevents it from being destroyed when landing on on or within 1" of an enemy model. However, the sheer mass would do nothing to prevent Misplaced or Delayed.

Another point to ponder if you want to be TFG, the monolith entry only specifies enemy models, not friendly models. So if the monolith were to scatter onto friendly models, per the BRB, it would roll on the mishap table and couple be destroyed on a 1 or 2.

Brother Ramses wrote:Another point to ponder if you want to be TFG, the monolith entry only specifies enemy models, not friendly models. So if the monolith were to scatter onto friendly models, per the BRB, it would roll on the mishap table and couple be destroyed on a 1 or 2.

Why would you be TFG? The Lith has ALWAYS mishapped when landing on friendly models.

How is it tfg even to play it mishapping on enemy models? Being tfg is exploiting a grey area of the rules, this is pretty clearly spelled out.

The fact that it doesnt do what it used to anymore is about as relevant as the price of tea in china.

Also it is important to call things what they are, keeps confusion at bay for the most part ...

njfed wrote:Long, long ago in a edition long forgotten.

The summer cottage isn't the only unit to have special rules that no longer work in all cases. Why should it be different than, say, Banshee masks and grot riggers? Those still work in some cases but 5th edition took away something. And let's not forget that some units get improved by the changes... people seldom complain about that even if their special rules weren't meant to do everything they do now.

I believe INAT rules in favor of the Banshees when charging through cover.