Bug or WAD

[choppinlt]

Let's play bug or WAD!
Case 1: Army given movement orders and is able to move 2 regions in the same turn. First region can overrun an unprotected town, then orders are given to end movement by assaulting the fort at the destination region. During the action phase the army fights in region 1, and wins easily. Then it moves in to region 2 and no assault takes place. Is this WAD, or a bug?

Screensho.jpg (303.77 KiB) Viewed 1909 times

Screenshot (4).jpg (282.68 KiB) Viewed 1909 times

[choppinlt]

Case 2:
In the first photo the army on the left was given orders to move in to the same region with the other army...

The attachment Screenshot (2).jpg is no longer available

During the action phase the army on the right arrives at the meeting point and a previously unseen enemy army attacks the waiting army. It *appears* that the second army hadn't arrived yet because I didnt seem them during the battle. My army wins in 1 round of combat, and pushes the enemy out. To my surprise I see the message in the pic below. It tells me that the second army was pushed back by an arriving enemy. Is this a bug or WAD?

Screenshot (2).jpg (281.62 KiB) Viewed 1908 times

[loki100]

#2 is WAD, there is a mechanic that means an army weaker than the defenders will stop their movement ('be pushed back') instead of fight etc. As ever, I'd suspect there is a random element to this calculation so it might sometimes happen even if you think you are committing a reasonably strong force

[choppinlt]

First off, sorry but something happened to that one picture...

Thanks Loki! Well I knew that an enemy force could pushback/prevent your force from entering a region, and that makes total sense. This example seems less intuitive, because my stationary army fought and defeated the enemy army in one round of combat BEFORE the reinforcing army arrived. Yet the reinforcing army was never allowed to arrive despite the stationary army winning a battle prior to arrival. I just bring it up in case this wasn't supposed to happen. If this is WAD I'm totally good with it. In fact I like that these types of incidents can happen.... after all, no plan survives contact with the enemy.

And what about Case 1?

[Pocus]

The first region in case 1 was not walled? I'm not certain then why the assault order was cancelled, I would need the save before the turn execution.

[choppinlt]

That is correct, the first region was unwalled. And the assault was not performed in the second region as ordered. I will email you the file.

On a related note, I'm routinely seeing the AI move in to a region, assault and take the region, then continue movement in to another region. Is this WAD? I have never figured out how to continue movement after ordering an assault if this is WAD. It wouldn't be the first time I couldn't figure something out...

[loki100]

its WAD, you can set the assault command to attack as you enter a region and then move on. Clearly a bit risky as you may stumble onto a large garrison but a good way to clear out a cluster of poorly defended regions

[choppinlt]

Thank you Loki!

[Pocus]

I looked in the save and I think that's WAD. You can move and assault and then continue moving, but you can't move, and then move again then assault.

I'm reluctant to change that as we are soon wrapping up the files for the official patch!

[Bullseye500]

What is WAD? Thanks.

[TimDee58]

Working As Designed