Charge Congestion

[ethan]

So what happens if two BGs are charging an enemy BG such that after the first BG charges and the enemy evades it is now in the path of the second BG? Does it matter if one charger is shock troops and the other is not?

[hammy]

So what happens if two BGs are charging an enemy BG such that after the first BG charges and the enemy evades it is now in the path of the second BG? Does it matter if one charger is shock troops and the other is not?

Then the evaders get hit by the second charge.

If two BGs charge one in different directions then the evader has to be very carefull selecting it's evade direction.

I have seen an evading BG end up in the path of a totally unrelated charge. That was rather messy

[rtaylor]

hammy,

You misunderstood who was who. Three BGs charged to converge on a single target enemy BG. The enemy BG evaded far enough that it couldn't be caught by any of them. Charging BG 1 rolled its VMD and pursued. Then charging BG 2 rolled a VMD that would put it into BG1's rear if it made a pure pursuit. As we played it, BG 2 contracted a file and moved beside BG 1. But is burst-through possible in this situation?

(I was ethan's opponent in that game, by the way.)

[hammy]

hammy,

You misunderstood who was who. Three BGs charged to converge on a single target enemy BG. The enemy BG evaded far enough that it couldn't be caught by any of them. Charging BG 1 rolled its VMD and pursued. Then charging BG 2 rolled a VMD that would put it into BG1's rear if it made a pure pursuit. As we played it, BG 2 contracted a file and moved beside BG 1. But is burst-through possible in this situation?

(I was ethan's opponent in that game, by the way.)

Right, we are talking chargers hitting other chargers....

Contracting a file is fine and sounds like the correct solution in this case. What happens if you can't fit bu contracting a file I really don't know. I will have to have a read and hope that one of the design team picks this up.

I take it you are talking about something like:

Code: Select all

1        3
 1  TT  3
  1    3
   2222

[nikgaukroger]

IIRC there is something about moving the BG that moves furthest first - after rolling VMD - although it may only be for pursuits thinking about it. If it does exist it may have helped the situation.

[rbodleyscott]

As far as I am aware the charging player can move his BGs in any order he chooses.

If as a result of one of them moving, the other one's charge becomes impossible, then it would have to be cancelled. (There is AFAIK no rule specifying this, but nor is there any rule specifying how to move an impossible charge).

[ethan]

IIRC there is something about moving the BG that moves furthest first - after rolling VMD - although it may only be for pursuits thinking about it. If it does exist it may have helped the situation.

In fact we did this and there was still congestion.

I believe RBS is correct, I read through the rules and the only thing that seemed to apply was "if there isn't room to charge cancel charge."

The only other question is would shock mounted (Cataphracts charging second) burst through non-shock (LH charging first)?

[ethan]

IIRC there is something about moving the BG that moves furthest first - after rolling VMD - although it may only be for pursuits thinking about it. If it does exist it may have helped the situation.

In fact we did this and there was still congestion.

I believe RBS is correct, I read through the rules and the only thing that seemed to apply was "if there isn't room to charge cancel charge."

The only other question is would shock mounted (Cataphracts charging second) burst through non-shock (LH charging first)?

[rtaylor]

As far as I am aware the charging player can move his BGs in any order he chooses.

Do you roll VMD for all charging BGs before moving any of them?

[davem]

When I saw this threads title, I thought Mayor Ken was a secret FOGger!!

[nikgaukroger]

LOL

Variable competition entry charge depending on what though? Number of knights?

[davem]

LOL

Variable competition entry charge depending on what though? Number of knights?

Nah! Double fee if you field Chelsea Tractors (Heavy Chariots)!!

[nigelb]

Hi - I faced a situation in my first game of FoG recently which I'm now not sure we resolved correctly.

I declared two charges - outflanking BG A against the rear of some enemy cataphracts, and LH BGs B & C against some enemy LH who were forward of the cataphracts. My initial thought was - charge A against the cataphracts first (who will stand to receive them); this will put BG A directly in the evade path of the enemy LH being charged by BGs B&C, within their minimum evade distance and the enemy LH should end up unable to evade my 2:1 charge.

On second reading of the rules, though, it seemed that all evade moves were done before all charge moves, with the result that the enemy LH managed to evade. In fact, with VMDroll of 6, they evaded past the line of BG A's charge into the cataphracts, and were left free and clear. Both my charging LH stopped short of the cataphract position.

So, the big question is (and there is no perfectly clear and unambiguous statement that I can see in the rules) - do you resolve all evades, then all charges, then all combats, or do you resolve each evade/charge/combat in turn?

I believe the rules indicate the former situation - on page 52 they say "troops responding to charges..." and the use of the plural "charges" suggests to me that all responses are done before any charges. The Full Turn Sequence chart suggests the same to me (Make evade moves... Make charge moves). But it would seem more practical to resolve each response/charge/combat sequence in turn. What is the correct interpretation?

[nigelb]

OOPS! Ok, I found it! Call me stupid - page 68 Sequence of Charges and Responses in a nice big bold heading, and I missed it. So each response and charge is carried out in turn, then all combats together. So my outflanking charge could have been in position to stop the LH evade.

Sorry to have added to the confusion and displayed my ignorance!

I won't forget it now, though!