Initial Rout

[zoltan]

Here's how I see it:

1. Charging BG declares that it will charge
2. Charged BG decides that it will evade
3. Charging BG indicates direction of its charge
4. Charged BG decides between its two options (if both available): evade in direction of charge or to its own rear
5. Charged BG (evader) rolls VMD
6. Evader turns either 90 or 180 degrees if applicable
7. Evader attempts to complete its VMD evade
8. Evader encounters friends it cannot interpenetrate
9. If at least one file of the evading BG can complete its VMD evade move by sliding sideways up to 1 base width, it does so
10. The remaining files of the evading BG are picked up and "fall in behind" the file that has completed its VMD (in this situation the tail of the evading BG is more likely to be caught by the charging BG).

[philqw78]

Here's how I see it:
8. Evader encounters friends it cannot interpenetrate
9. If at least one file of the evading BG can complete its VMD evade move by sliding sideways up to 1 base width, it does so
10. The remaining files of the evading BG are picked up and "fall in behind" the file that has completed its VMD (in this situation the tail of the evading BG is more likely to be caught by the charging BG).

No any base may only shift up to 1 base width. If any have to shift more the BG does not shift at all. So in your case the remainder are not 'picked up' and placed behind. The evaders instead burst through.

[petedalby]

IE

A = enemy chargers very close to B
B = target of charge
C = friends of B
! = table edge

AA!
AA!
BB!
BB!
C

1) does the left file of B fall in behind the right file as the right file evades?
or
2) does B have to change frontage before any move (which it cannot do) and hence have to burst through C. It would be a a shame if 2 was correct as its a geometric anomaly as well. When contracting to evade the BG would certainly not form a nice neat culumn first in order to fit through. They would clamour and just squeeze through like a fire at a football stadium. This would be slower so they would be more likely to get caught but that is already reflected to the increased depth of B's formation.

Sorry to disagree with your previous respondent gozerius, but if the right hand file of B falls in behind the left hand file of B, which then shifts to the left to avoid C, the right hand file of B will have shifted by 2 base widths - which is not permitted.

In the example you have posted B will burst through C with no shift or contraction permitted.

[expendablecinc]

Here's how I see it:

1. Charging BG declares that it will charge
2. Charged BG decides that it will evade
3. Charging BG indicates direction of its charge
4. Charged BG decides between its two options (if both available): evade in direction of charge or to its own rear
5. Charged BG (evader) rolls VMD
6. Evader turns either 90 or 180 degrees if applicable
7. Evader attempts to complete its VMD evade
8. Evader encounters friends it cannot interpenetrate
9. If at least one file of the evading BG can complete its VMD evade move by sliding sideways up to 1 base width, it does so
10. The remaining files of the evading BG are picked up and "fall in behind" the file that has completed its VMD (in this situation the tail of the evading BG is more likely to be caught by the charging BG).

In my example the right file can complete its vmd without sliding at all.
In this case would the left file simply fall in behind them - sliding one base width to do so or does the BG have to change frontage first.

It matters becasue it makes it a uselfu strategy to get right in LH face so they cant squirt though small gaps as easily.

[petedalby]

In my example the right file can complete its vmd without sliding at all.

Okay - but that's not how it appears in your original post? It appears to be directly lined up with C.

In this case would the left file simply fall in behind them - sliding one base width to do so or does the BG have to change frontage first.

Yes - the base falls in behind - there is no need to for the BG to change frontage first - provided it does not shift more than 1 base width.

Check out the diagrams on Pages 164 & 166.

On page 164, a 6 base BG fits through a 1 base gap - because no single base slides by more than 1 base width.

If that same 6 base BG were to be in the situation shown in the 2nd diagram on Page 166, with the extra 2 bases added to the left of the BG, it would not be able to avoid bursting through the MF behind.

Hope that makes sense - this is quite an important part of the game and it's important to understand it correctly - especially if Zoltan is umpiring at the IWF.

[batesmotel]

IE

A = enemy chargers very close to B
B = target of charge
C = friends of B
! = table edge

AA!
AA!
BB!
BB!
C

1) does the left file of B fall in behind the right file as the right file evades?
or
2) does B have to change frontage before any move (which it cannot do) and hence have to burst through C. It would be a a shame if 2 was correct as its a geometric anomaly as well. When contracting to evade the BG would certainly not form a nice neat culumn first in order to fit through. They would clamour and just squeeze through like a fire at a football stadium. This would be slower so they would be more likely to get caught but that is already reflected to the increased depth of B's formation.

Sorry to disagree with your previous respondent gozerius, but if the right hand file of B falls in behind the left hand file of B, which then shifts to the left to avoid C, the right hand file of B will have shifted by 2 base widths - which is not permitted.

In the example you have posted B will burst through C with no shift or contraction permitted.

From the rules on page 67, under evaders encountering obstructions:

Provided that they do not shift more than one base width sideways, bases that cannot get past an obstruction can be moved to the rear of those bases that have completed their evade move. In this situation the BG is more likely to get caught , as its rear will not move as far as its front.


As long as the file of B closest to the board edge evades far enough that the other file can fall in behind the evaded file, then B will not have to burst through C. /the files are moved sequentially in this case and no explicit formation change is performed.

Chris

[zoltan]

In my example the right file can complete its vmd without sliding at all.

Okay - but that's not how it appears in your original post? It appears to be directly lined up with C.

In this case would the left file simply fall in behind them - sliding one base width to do so or does the BG have to change frontage first.

Yes - the base falls in behind - there is no need to for the BG to change frontage first - provided it does not shift more than 1 base width.

Check out the diagrams on Pages 164 & 166.

On page 164, a 6 base BG fits through a 1 base gap - because no single base slides by more than 1 base width.

If that same 6 base BG were to be in the situation shown in the 2nd diagram on Page 166, with the extra 2 bases added to the left of the BG, it would not be able to avoid bursting through the MF behind.

Hope that makes sense - this is quite an important part of the game and it's important to understand it correctly - especially if Zoltan is umpiring at the IWF.

Which I am (brew hoo haaa haah!). So bases may be "picked up and placed behind another file" as long as neither the other file, nor the picked up bases, have moved more than one base width to the side (if required) to pass by a friendly BG.

[petedalby]

Which I am (brew hoo haaa haah!). So bases may be "picked up and placed behind another file" as long as neither the other file, nor the picked up bases, have moved more than one base width to the side (if required) to pass by a friendly BG.

Okay - I think you have it.

If any doubt remains I'll happily post some photos to illustrate the point for you? A picture paints a thousand words and all that.

[zoltan]

If any doubt remains I'll happily post some photos to illustrate the point for you? A picture paints a thousand words and all that.

Do post a picture (I've been having fun with that myself) as it will help others. Nothing like a serious comp to force one to read the rules and figure out finer points.

[expendablecinc]

If any doubt remains I'll happily post some photos to illustrate the point for you? A picture paints a thousand words and all that.

Do post a picture (I've been having fun with that myself) as it will help others. Nothing like a serious comp to force one to read the rules and figure out finer points.

Thats why I brought it up. Locally I have given a bum steer advising folks that the evaders change frontage (if they can) but thats not the case. I guess when all else fails, read the rules.

[hazelbark]

I guess when all else fails, read the rules.

[ShrubMiK]

Steady on chaps, can't have you setting such a dangerous precedent!!!