_[FDB] (bRC4) Rear charge not showing POA

[FedeM]

Hi,

Reach to the following situation where the POA for rear charge is not taken into consideration.

Console:

0]BG[50] Veteran heavy cavalry was selected
[2] BG[50] already took an anarchy charge test this turn
[2] BG[50] charges BG[38]
[3] BG[38] already took an evade test this turn
[2] BG[50] Veteran heavy cavalry impact attacks BG[38] Javelinmen
[3] BG[50] vs BG[38] combat -> quality re-rolls are enabled
[3] BG[50] impact combat dice no: 4 *2/3 => 3 dice
[3] 4(most BG's are rolling 4 dice in combat) (base)
[3] *2/3(dis,Drd,drd) BG[50]
[3] BG[38] impact combat dice no: 2 => 2 dice
[3] 2(LF vs no LF,frg) (base)
[3] BG[50]'s impact combat POA: +1 = 1
[3] +1(LSpMT vs any, no other net POA) BG[50] vs BG[38]
[3] BG[38]'s impact combat POA: +1 = 1
[3] +1(LSpFT vs any, unless charging shMT) BG[38] vs BG[50]
[3] BG[50] dice roll: 3,[(1)5],[6] (0 POA [4,5,6]) => 2 hits..
[3] BG[38] dice roll: [4],[5] (0 POA [4,5,6]) => 2 hits..
[3] BG[50](2 hits) vs BG[38](2 hits) combat => draw
[3] BG[38] lost 1.52% (16) strength
[3] BG[50] lost 2.07% (21) strength
[2] BG[50] Veteran heavy cavalry was deselected


tks

[cothyso]

considering your screenshot, you've previously moved the MT BG (as this is only has MP left for only 1 hex movement), and its turn start position must have been outside of the rear area of the to-be-charged EBG.

this not a bug, and intended as so, accordingly with the rules.

// GAMEPLAY RULE - [Combat Impact]: a rear hex attack is considered a rear charge only if the charging BG's position at the start of the current turn phase was in charged BG's rear area.

Again, in FoG(U) you charging BG's turn start position must be in charge EBG's rear area, to count as a rear charge. you can no longer "cheat" by moving the BG in EBG's rear area first, then do a rear charge (as in old FoG(RB), which wasn't preventing this)

[FedeM]

Hi Dan,

Aa far as I know that rule applies to the automatic cohesion loss when charged from the rear from the correct angle and not to the +2 POA that you must have when charging an enemy BG rear.

Here you have the same example from FOG RB.
Do not know why the LF kept his POA though. The same happens when tu charge a LH rear I think. Going to check.

I didnt mive the BG on purpose before charging. Just an accident.






Cheers!

[cothyso]

Manual uses the same exact wording for all three cases:

Code: Select all

A battlegroup, other than skirmishers, charged in its rear by an enemy, other than skirmishers, will suffer an instant cohesion loss on contact.
A battlegroup of skirmishers, charged in its rear by any enemy will suffer an instant cohesion loss on contact.
A battlegroup charged in its rear will always suffer the maximum combat penalty difference during impact combat.

Wiki is stating that you would retain the +2 rear charge POA even when not starting the charge from the charged BG's rear area, tough..

Your FoG(RB) examples are charging from inside charged BG's rear area, try to reproduce it by charging the rear from the flank line, or from front, please.

The FoG(RB)'s +1 POA for the charged EBG while having +2 rear charge POA for the charging BG seems to be a bug..

[cothyso]

modified for revision 690

Also modified the used wording: "charge in the rear" (a charge made in one of charged BG's rear hexes) and "rear charge" (a charge in the rear that starts from within charged BG's rear area).

Still waiting for confirmation as working as so in FoG(RB) v1.8.1..

[FedeM]

Hi Dan,

Here we are:

No Autom loss of cohesion but it keeps the +2 POA for the rear charge and 0 POA for the defender.



Tks

[cothyso]

Yes, that should do it, thank you.