Integrity
I have verified my game files (on Steam)
YesI have disabled all mods
YesRequired
Summary
3 bugs 1 screenshot: Armies not advancing with front when it merges, armies being calculated into front advantage before they arrive, bad routingDescription
The war shown in the screenshot initially had two fronts, on the northern and southern ends of the Siamese Radical Revolt. As soon as Siamese Revolt Tessarim was occupied from the south, that brought the two frontlines close enough for them to merge. This caused three issues:1. The army on the southern front did not automatically move to the merged front, like what usually happens when fronts advance. Instead, it started moving to the nearest HQ.
2. When I manually sent it to the new merged front, it was immediately factored into the front advantage for that front, even though it's 70 days away from actually being there. This seems to be a visual bug only, not affecting actual front battles.
3. This troop movement should not take 70 days. It's only taking that long because it's choosing a nonsensical route. It seems to be highly prioritizing moving through Japan's own vassals (Johore and Cambodia) even when doing so takes much longer than if they just moved through allied (Siamese) or occupied territory, and in fact results in more time spent in Siamese territory as well. If they just went via the most easily-accessible friendly shorelines, this trip would probably take 2 weeks. Instead they're pointlessly plodding through the Malay and Cambodian jungles.
Steps to reproduce
All three are visible by loading the attached save game. #2 is easily reproducible in almost any troop movement. #1 can be reproduced by setting up any situation with fronts on opposite sides of a small country.Game Version
1.9.8OS
WindowsAdditional
Bug Type
OtherSave Game
View attachment badarmymovement.v3Attachments

Player Pain
5
Last edited: