Line of attack/charge wonkiness?

[Fodderland]

In the below image, my cav SHOULD swing down and then right, to rear-attack the Swiss Keil. But if allowed to autopath to the Keil, he wants to move lower-right first (see the highlighted square) and thus lose out on being able to rear-hit. And, if I manually override the autopathing and manually force him to go down first, he then, somehow, doesn't have enough AP left to attack at all.

Not_enough_AP_2_squares.jpg (128.96 KiB) Viewed 1992 times

[Fodderland]

So, next I moved the horse to my cav's right, down into the highlighted square, blocking it. Then, tried moving the cav again - and sure enough, THIS time, he's got enough AP to move down and then attack. WTH? Btw - still LOVING this game

But_Now_Enough_Mob_with_cav_in_way.jpg (128.12 KiB) Viewed 1990 times

[Athos1660]

This is known and due to the pathfinding of the engine.

btw here, your cavalry can only charge by the flank, not by the rear, so the Keil's cohesion won't drop. Your cav should be on the nearby square on the left hand side when it starts its move (ie. move strictly diagonally).

Great game indeed. Have fun

[rbodleyscott]

The engine does not know your intentions, and does not apply artificial intelligence to the path it finds. Sometimes you can get round this by moving your unit one square at a time, but not in this case because the moves would involve two 45 degree turns. (These are ignored when the unit moves the whole move in one go. In real life, it would be easier for troops to obey the order "charge!" than "go over to there, and then charge").

Edit: Removed erroneous statement.

[Cronos09]

In the second case, it is the rear charge. Therefore, this question arose that the difference as a result of the 2 charges is significant I think.

According to the script condition the angle the enemy is presenting to the attacker's position should be more than 138 degr. That is a charge from any tile within the red sector will be a rear attack if its path lies through the selected/highlighted tile.

[Athos1660]

In the second case, it is the rear charge.

You're right, Cronos.





It has its logic : in the second case only, the charger hits the keil from the square just behind it.

[rbodleyscott]

In the second case, it is the rear charge. Therefore, this question arose that the difference as a result of the 2 charges is significant I think.

According to the script condition the angle the enemy is presenting to the attacker's position should be more than 138 degr. That is a charge from any tile within the red sector will be a rear attack if its path lies through the selected/highlighted tile.

Of course you are right, my mistake.

[w_michael]

In the original post, the default move only requires one 45 degree turn, whereas the desired move requires two 45 degree turns. I suspect that has a lot to do with the default movement path, and why a manual move doesn't have enough MP to charge.

[Cronos09]

I think that in the first case, when we move the winged hussars unit manually vertically down, it loses 4AP + Free Turn (12AP are left). Then it must turn 45 degrees and charge diagonally, which requires 8 + 6 = 14AP.
In the second case, we also have two 45 degree turns. But they happen during one movement and the angle of turn is calculated at the start of the move:
angle = GetAngleFromTile(tilex, tiley, me) ; //get the angle the unit is presenting to the denoted tile, 0=looking straight at it, 180= it is directly behind them.
I think that with this movement the 'Free Turn' is not even lost.