In #1 the group moves sideways to “line up” outside the Threat Zone (TZ) in the middle of a move. In #2 the group moves sideways inside the TZ. Both moves end in contact.
I think these aren’t allowed because the last paragraph on page 28 says
“[A group move cannot] include … any sideways movement or oblique movement except to line up in front edge combat, …”The issue for clarification is the timing of the sideways move. Other people have said for #2 that as long as the move ends in combat the timing is not crucial because once in the TZ you may choose to line up (page 33).
If this is correct then the wording on page 28 should be changed. If not the rule should be played as written. Hence the need for clarification.
Update: Wed, 21 Jan 2009
Well after two and a half months a clarification of sort has emerged. I posted this on the DBMMlist as part of a discussion of items that needed clarifying. Chris Handley, who was heavily involved in play testing the rules with Phil Barker, replied (see http://tinyurl.com/9la9pe) as follows:
So move #1 is illegal for a group whilst #2 is allowed as the group is in the Threat Zone (TZ) and the timing is immaterial. It’s nice to get clarity although I think the section on page 28 could use a tweak or two.
Having finally sorted this issue I’m not sure whether I actually like it as a mechanism. It’s obviously there to ensure contact happens as easily as possible but it allows “sloppy” play in that you don’t have to worry about blocking your own attacks. I’ll have to see how it works out in practice. This will certainly change the way I look at attacking moves.
Updated: Tue, 26 May 2009
Today, Phil Barker posted a proposal on the DBMM list which, if it makes it into DBMM v1.1, would formally clarify this issue:
“Any move that will enter; or starts in, or at the front edge of, an enemy Threat Zone (TZ) must immediately line up opposite[,] or in front edge-to-front edge combat with[,] the TZ-ing [sic] element most directly in front.”
Let’s see if it survives the DBMMlist and makes it into DBMM v1.1 by the end of the year.