Jump to content

Rage and multi-model unit


Recommended Posts

Well.. earlier this week we had a discussion about how one is allowed to move a unit of DC in the movement phase and what isn't allowed.

I consider that discussion closed, but I had something else I wasn't 100% sure about.

 

Rage forces one to move towards the 'nearest visible enemy' now.. how does this work in a multi model unit.

For an example.. look at the image below: (fear my paint-fu!)

http://farm5.static.flickr.com/4081/4823841584_f102a38534.jpg

 

Now.. the black line is impassable terrain that also blocks all sight.

The red/black blobs are a DC unit

The Green blobs are Orc Warbosses about to get a beating.

 

Which one will get the beating though?

 

The below Orc is closest to the unit, but is only visible for 1 model. And, that specific model also has the above Orc closer to him.

 

So, how does closest visible get defined?

 

1. For each model in the unit, and the model with the closest visible enemy defines where the whole unit goes?

2. Or should we determine if the closest model is visible to the unit as a whole and not mind if the model he is closest to is actually also the one that is able to see him?

 

I feel the second option is what should be done. USR is a Unit specific rule, not model specific so everything you determine should work on the unit and not on individual models (just like my opinion with the movement discussion)

 

Thoughts on this one?

Link to comment
https://bolterandchainsword.com/topic/207154-rage-and-multi-model-unit/
Share on other sites

Easy thing. The DC Squad hast to move to the above Orc because they cannot see the other one behind the LOS Blocker and the DC model which can see this Warboss is much closer to the above one. And you have to move towards the closest visible unit.
Easy thing. The DC Squad hast to move to the above Orc because they cannot see the other one behind the LOS Blocker and the DC model which can see this Warboss is much closer to the above one. And you have to move towards the closest visible unit.

 

But that is my point.. For the DC Unit, the orc below is visible because it is visible for 1 of its models. And it is clearly the closest as well. It is only not visible for the model it is closest to, it is still visible to the unit.

 

Why do you think the whole squad needs to follow the model that can see both and has 1 warboss closer to itself then the rest of the unit has?

Dues is correct. The line blocks LOS, making the green blob at the top of the drawing the closest visible enemy.

 

Easy thing. The DC Squad hast to move to the above Orc because they cannot see the other one behind the LOS Blocker and the DC model which can see this Warboss is much closer to the above one. And you have to move towards the closest visible unit.

 

But that is my point.. For the DC Unit, the orc below is visible because it is visible for 1 of its models. And it is clearly the closest as well. It is only not visible for the model it is closest to, it is still visible to the unit.

 

Why do you think the whole squad needs to follow the model that can see both and has 1 warboss closer to itself then the rest of the unit has?

 

 

You measure from a DC model that can see to the target. The blob behind the wall is close to models that can not see it, but the only model that can is pretty far away. Going from models that can see to the enemy, the one on the top is clearly the closest.

i concour with deus and jamesI, see as the majority of the unit can see the above model.

 

well imagine, in the heat of the battle, the death company are running full on towards that above warboss, and then theres one single dc going: 'hey guys over here!?' chances are, hed be igored, or just join the others when he saw what they were going for. personally, i base mine of what the majority of the squad can see.

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.