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 we had this situation happen twice last night, once in two different games going on, and I was wondering how everyone thinks this should be played.

In both situations we had units that were already on the board make use of the Deep Strike rules (Ork Weird Boy with "Ere We Go and a unit of Sternguard deep striking out of a stormraven) both resulted in a mishap and both got the Delayed result. One of these happened in my game and the other was on the next table so they asked how to resolve it, my answer was the put the units into Ongoing Reserves. What do you guys think of this resolution.

Did this not get FAQ'd, or was that a 5th edition FAQ that got dropped from 6th?

I have always played they "go back" into reserves, so Ongoing Reserves in this case. I think they get to deepstrike again, nto walk on again, the last time this was FAQ'd.

Not sure on 'Ere We Go, but doesn't the rules for the Stormraven say that if one model cannot be placed the unit is destroyed?

 Happyjew wrote:
Not sure on 'Ere We Go, but doesn't the rules for the Stormraven say that if one model cannot be placed the unit is destroyed?

I believe that's the grav chute option for vendetta. Stormraven skies of fury don't have that verbiage.

 hyv3mynd wrote:

 Happyjew wrote:
Not sure on 'Ere We Go, but doesn't the rules for the Stormraven say that if one model cannot be placed the unit is destroyed?

I believe that's the grav chute option for vendetta. Stormraven skies of fury don't have that verbiage.

Oh it definitely does!

 CrashCanuck wrote:
So we had this situation happen twice last night, once in two different games going on, and I was wondering how everyone thinks this should be played.

In both situations we had units that were already on the board make use of the Deep Strike rules (Ork Weird Boy with "Ere We Go and a unit of Sternguard deep striking out of a stormraven) both resulted in a mishap and both got the Delayed result. One of these happened in my game and the other was on the next table so they asked how to resolve it, my answer was the put the units into Ongoing Reserves. What do you guys think of this resolution.

you were correct.

for the orks, 'ere we go Is resolved like a deep strike, if you mishap you have to abide by the table and follow the results and in this case they go into ongoing reserves.

I'd assume the sternguard would work the same way if they count as deep striking, but I don't have a guard dex to check the wording.

Skies of Fury is pretty clear:

brb wrote:
If it scatters, immediately take a dangerous terrain test....

if any of the models cannot be deployed, the entire unit is destroyed....

So, the Sternguard would have been removed from play.

I believe The orks are different. Admittedly, I don't have an ork codex in front of me so you probably want to read their specific rule to see if it says follow the rules for Deep Striking. If so, then they go into ongoing reserves.

I just let the Weirdboy and the unit he was with walk on the next turn as if they had gone into Ongoing Reserves, the Sternguard never got the chance to come back on anyway as the game ended at the bottom of the turn in which they got "delayed"

I'm not familier with the Ork power, but if they went into ongoing reserves because of a deep strike mishap, shouldn't they come in via deep strike the next turn? I don't think I would let them walk on.

The ork unit would go into ongoing reserves and would have to walk on not deepstrike because the unit does not have the deepstrike rule.

RAW, they do not have deepstrike rule, so they would would walk on.

For fun and fluffy play? Have them go into ongoing reserves, and deepstrike in. Perhaps they got delayed in the Warp on their way in?

Ere we go grants them deepstrike to redeploy, if they get a mishap that leads to delayed they will still deploy based on the power that took them off the board, so can still deepstrike.

Delayed in warp doesnt change how they would have been deployed, it delays when they would be deployed.

blaktoof wrote:
Ere we go grants them deepstrike to redeploy, if they get a mishap that leads to delayed they will still deploy based on the power that took them off the board, so can still deepstrike.

Delayed in warp doesnt change how they would have been deployed, it delays when they would be deployed.

Not true.
Delayed simply puts them into ongoing reserve. Nothing more, nothing less.
They must then arrive as per the rules of ongoing reserve. They don't have Deep Strike, so cannot use it.

maceria wrote:
RAW, they do not have deepstrike rule, so they would would walk on.

For fun and fluffy play? Have them go into ongoing reserves, and deepstrike in. Perhaps they got delayed in the Warp on their way in?

Fluffy play would be that they walk onto the battlefield because the weirdboy missed the landing by a few miles and didn't have enough energy to try again.