weird situtation

rich0101 · Post by **rich0101** » Wed Jun 25, 2008 5:29 pm

This weekend at the tournament this is the situation. I had a BG of 6 LH that got charged in the flank by a BG of 4 LH. Then another BG of LH comes in as support, but how many dice would the supporting BG get and once I show how I was facing would I be considered as fighting in two directions.

SSSS
M>><H>><H

The S's are support and the M are facing up and the >> are 4 LH facing right. <<are his 4 LH that charged facing left.
[/list][/code]

hammy · Post by **hammy** » Wed Jun 25, 2008 5:42 pm

I tried to make sense of your diagram and failed.

Could you try and edit the diagram then put it in a code box like:

Code: Select all

AAA
AAA
 >>B<<
 >>B<<

rich0101 · Post by **rich0101** » Wed Jun 25, 2008 5:52 pm

I don't know how to use those functions.
[/img][/list]

rich0101 · Post by **rich0101** » Wed Jun 25, 2008 5:55 pm

SSSS
M>><H>><H
S being support BG, M being me and the 2 M's facing his support BG, >> being my 4 LH facing his 4 LH (<H)

rich0101 · Post by **rich0101** » Wed Jun 25, 2008 5:58 pm

every time i type in the set up it messes up when I hit post.

Jason_Langlois · Post by **Jason_Langlois** » Wed Jun 25, 2008 6:44 pm

Using the <and> leads to your post probably being interpreted as HTML code, maybe?

hammy · Post by **hammy** » Wed Jun 25, 2008 9:57 pm

Type the diagram with the correct number of spaces (one space per blank) then highlight just the diagram and click the code button at the top of the post a reply window.

I think you are trying to get something like:

Code: Select all

SSSS
M>><H>><H

But the exact possition of SSSS relative to the others is difficult to fathom.

hammy · Post by **hammy** » Wed Jun 25, 2008 10:00 pm

OK, now I am confused. It looks like the >> and < symbols are what is causing the problem.

Try doing it with caps for facing one way and lower case for facing the other sort of like this:

Code: Select all

SSSS
MmmHH
MmmHH

rich0101 · Post by **rich0101** » Thu Jun 26, 2008 12:34 am

Code: Select all

SSSS
MmmHH
MmmHH

m is facing H, H hit m in the flank, M hasn't had a chance to face H because of only being able to effect one file in the movement phase. S is facing H but is an overlap for the combat on H's side. M is facing S

lawrenceg · Post by **lawrenceg** » Thu Jun 26, 2008 7:13 am

rich0101 wrote:
Code: Select all
SSSS
MmmHH
MmmHH
m is facing H, H hit m in the flank, M hasn't had a chance to face H because of only being able to effect one file in the movement phase. S is facing H but is an overlap for the combat on H's side. M is facing S

Do I understand correctly that what happened is:

Code: Select all

initial position

SSSS

MMM          HH
MMM          HH

Code: Select all

Impact phase, H charges M in flank. The contacted bases of M turn to face H (and become "m")

SSSS

MMmHH
MMmHH

Code: Select all

Manouevre phase, S moves its front edge into the flank of m at the corner (intended to count as a postion of overlap support)  , incidentally contacting the front of MM

SSSS
MMmHH
MMmHH

If that is what you mean then I think SSSS's move was not legal. It could only get into this position by charging in the impact phase because it is moving bases into a position where thay fight directly, not as overlaps.

If SSSS moved in by a charge in the impact phase then MMM would be fighting in two directions.

rich0101 · Post by **rich0101** » Thu Jun 26, 2008 3:15 pm

Thanks I appreciate it.