Switch Theme:

[IG] Consolidate Squads - How does it work when used on a squad that Fell Back and one that did not?  [RSS] Share on facebook Share on Twitter Submit to Reddit
»
Author Message
Advert


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.




Made in ca
Twisted Trueborn with Blaster



Ottawa

Consolidate Squads: Use this stratagem at the end of your Movement phase. Choose an Infantry Squad from your army that is within 2" of another of your Infantry Squads from the same Regiment. You can merge these two squads into a single unit and they are treated as such for the rest of the battle.

My opponent and I hit a snag when I decided to use the Consolidate Squads stratagem to merge the remnants of a squad that had just Fallen Back from close combat with a squad that had not been in close combat yet. Would the merged squad be able to shoot normally, without being given the Get Back In The Fight! order?

I'm inclined to think they are treated as a whole new squad, who therefore have not Fallen Back since they just sprang into existence, but I'm aware this interpretation is open to abuse. Since we could not agree, I decided not to Consolidate Squads after all, to keep things simple.

I would still like to know anyone's thoughts on the matter. The Consolidate Squads rule can cause a lot of headaches.


.

This message was edited 2 times. Last update was at 2018/08/12 14:59:34


Cadians, Sisters of Battle (Argent Shroud), Drukhari (Obsidian Rose)

Read my Drukhari short stories: Chronicles of Commorragh 
   
Made in us
Confessor Of Sins





Tacoma, WA, USA

The rules simply do not address the issue one way or the other.
   
Made in gb
Norn Queen






This was brought up day 1 of the Codex's release. In short, we don't have the rules necessary to determine the result. It needs an errata, but will most likely receive a Special Snowflake FAQ some time in 2157, since GW don't actually care about making their overpriced rules work.

This message was edited 1 time. Last update was at 2018/08/12 20:13:07


 
   
Made in us
Longtime Dakkanaut




Wichita, KS

I agree 100% that we don't know how this works. The way I play it is I take the most restrictive of the 2 squads. ie. if one squad fell back, I treat the combined squad as having fallen back. If one squad ran, I treat the combined squad as having run.
   
Made in gb
Lord of the Fleet






London

tag8833 wrote:
I agree 100% that we don't know how this works. The way I play it is I take the most restrictive of the 2 squads. ie. if one squad fell back, I treat the combined squad as having fallen back. If one squad ran, I treat the combined squad as having run.


I agree, on the assumption that part of the unit falling back is still counting as the whole unit falling back, therefore preventing them shooting.
   
Made in us
Longtime Dakkanaut





As far as actual rules go there is no way to rule one way or the other. I would leave it to a roll off to see if they count as a single unit taking on ALL active affects from both units or as a new unit that inherits NONE of the previous affects of the previous units.

 
   
Made in fi
Locked in the Tower of Amareo





Yet another example of how you cannot actually play the game 100% RAW. You hit this, game freezes down. However you proceed from there is no longer 100% RAW. So either you don't play 100% RAW or game freezes eternally there.

This message was edited 1 time. Last update was at 2018/08/15 05:21:30


2024 painted/bought: 109/109 
   
Made in gb
Norn Queen






tneva82 wrote:
Yet another example of how you cannot actually play the game 100% RAW. You hit this, game freezes down. However you proceed from there is no longer 100% RAW. So either you don't play 100% RAW or game freezes eternally there.
No, the game doesn't freeze because you have The Most Important Rule. This isn't a case of contradictory instructions like the multiple wounded models issue, this is a case that is explicitly the reason for TMIR.

The game is perfectly playable 100% RaW so long as you avoid the two situations where the game legitimately does break.

For reference:
In a game as detailed and wide-ranging as Warhammer 40,000, there may be times when you are not sure exactly how to resolve a situation that has come up during play. When this happens, have a quick chat with your opponent and apply the solution that makes the most sense to both of you (or seems the most fun!). If no single solution presents itself, you and your opponent should roll off, and whoever rolls highest gets to choose what happens. Then you can get on with the fighting!
This isn't a case where the RaW is clear and leads to a bad result, this is a situation where the RaW is unclear (because of course it is), and thus TMIR kicks in.

This message was edited 2 times. Last update was at 2018/08/15 05:29:42


 
   
Made in gb
Emboldened Warlock




Widnes UK

RAW - ????
HIWPI - Model by model, if a model was part of the unit that fell back it can't shoot, if it wasn't it can shoot.

Ulthwe: 7500 points 
   
Made in us
Never Forget Isstvan!






If we look at a similar stratagem (mob up) it actually kills off the smaller squad and adds them to the big one.

This isn't exactly the same as form up, but we can look at it for similar rules interactions as it is the more recent of the two stratagems.

JOIN MY CRUSADE and gain 4000 RT points!
http://www.eternalcrusade.com/account/sign-up/?ref_code=EC-PLCIKYCABW8PG 
   
 
Forum Index » 40K You Make Da Call
Go to: