Author Topic: Unintended (?) consequences of sponno/gap rules in 2.0  (Read 2221 times)

0 Members and 1 Guest are viewing this topic.

LawrenceG

  • Guest
Unintended (?) consequences of sponno/gap rules in 2.0
« on: October 17, 2010, 01:56:46 PM »
Warband A and B must make spontaneous advances.



I decided to move A first.

It goes straight ahead and hits C,




then pivots to face the same diection as C and ends its move. It ends closer to the previously nearest enemy element  X so it can't use the first bullet to contact X.



Then B advances. A straight ahead move would contact X, but in doing so B has moved in the narrow space between A and X, which is not sufficient for its frontage (depending on in which direction you measure it). THis is not permitted (top of page 32).




Therefore B moves straight ahead until it reaches the gap and then must stop. This ends closer to X so it can't use any of the bullets to do other stuff.

The net result of this is that neither A nor B could contact the enemy in front of them.

Is there anything open to interpretation which I could interpret differently to allow the elements to get into contact?

LAP1964

  • Guest
Re: Unintended (?) consequences of sponno/gap rules in 2.0
« Reply #1 on: October 18, 2010, 01:22:57 AM »
"It is an absolute requirement that troops that would move into close combat in real life must do so in the game."
So what is stopping A from moving into CC,and B moving into an overlap?

LES

landmeister

  • Guest
Re: Unintended (?) consequences of sponno/gap rules in 2.0
« Reply #2 on: October 18, 2010, 08:21:53 AM »
"It is an absolute requirement that troops that would move into close combat in real life must do so in the game."
So what is stopping A from moving into CC,and B moving into an overlap?

LES

I'm afraid Larry is right. The only way to move A into CC is cheating.  :-[ Certainly this is an unintended collateral effect of current wording.

Valentinian Victor

  • Guest
Re: Unintended (?) consequences of sponno/gap rules in 2.0
« Reply #3 on: October 19, 2010, 11:24:51 AM »
The easiest and most logical solution to this whole question would have been to have let group B sponno into element X. This would have led group B hitting the left front corner of X, which is a legal contact. The player controlling the group that included X then has two choices, he either leaves X in place and takes a -1 as per the rules, or he lines up in contact with group B. Group A could have moved forward to form an overlap with Group B if there is room to do so, which looking at that photo there is just enough room to do this.

I cannot fathom why a player would attempt to put Group A into contact as Group B is the most logical group to do this?

LawrenceG

  • Guest
Re: Unintended (?) consequences of sponno/gap rules in 2.0
« Reply #4 on: October 19, 2010, 01:22:51 PM »
The easiest and most logical solution to this whole question would have been to have let group B sponno into element X. This would have led group B hitting the left front corner of X, which is a legal contact. The player controlling the group that included X then has two choices, he either leaves X in place and takes a -1 as per the rules, or he lines up in contact with group B. Group A could have moved forward to form an overlap with Group B if there is room to do so, which looking at that photo there is just enough room to do this.

I cannot fathom why a player would attempt to put Group A into contact as Group B is the most logical group to do this?

It seemed like a good idea at the time.

Besides, in this case B couldn't contact X by moving first for the same reason it couldn't contact it moving second, although a reinterpretation of the "move in a space insufficient for its frontage" rule would fix that.

Valentinian Victor

  • Guest
Re: Unintended (?) consequences of sponno/gap rules in 2.0
« Reply #5 on: October 19, 2010, 01:46:55 PM »
The easiest and most logical solution to this whole question would have been to have let group B sponno into element X. This would have led group B hitting the left front corner of X, which is a legal contact. The player controlling the group that included X then has two choices, he either leaves X in place and takes a -1 as per the rules, or he lines up in contact with group B. Group A could have moved forward to form an overlap with Group B if there is room to do so, which looking at that photo there is just enough room to do this.

I cannot fathom why a player would attempt to put Group A into contact as Group B is the most logical group to do this?

It seemed like a good idea at the time.

Besides, in this case B couldn't contact X by moving first for the same reason it couldn't contact it moving second, although a reinterpretation of the "move in a space insufficient for its frontage" rule would fix that.

Does Group A have to line upto face X taking into account that as Group B will hit the corner of X, group A will then end up as an overlap with Group B? As Group A is moving through X's TZ it does not have to line up as on page 33 it specifically states '(and any moving in an enemy TZ may)'.

Set up the same situation again and try out what I suggested, I cannot see what I think being a problem at all.

landmeister

  • Guest
Re: Unintended (?) consequences of sponno/gap rules in 2.0
« Reply #6 on: October 19, 2010, 03:08:53 PM »
Does Group A have to line upto face X taking into account that as Group B will hit the corner of X, group A will then end up as an overlap with Group B? As Group A is moving through X's TZ it does not have to line up as on page 33 it specifically states '(and any moving in an enemy TZ may)'.

Set up the same situation again and try out what I suggested, I cannot see what I think being a problem at all.

I think this is a better solution. Group A may line up before advancing as it begins its move within X's TZ, so problem solved! Sponno moves MUST obey TZ rules, and lining up paralel to an enemy is one of them. Then it can move forward as no sponno priorities are avoided. It can end closer to its closest enemy moving forward.  ;)