When I'm sending reinforcements to join defenders at province center they start attacking before they reach province center. I'm not giving an attack command, just a move command to province center from far away. Under what circumstances will such a unit decide to attack instead of joining the defending stack? It seems to be happening to all my units. It's getting very expensive. Is this something newly broken?
7 Replies
17 Nov 2022, 10:17
Freezy tried to explain this a while ago, though he didn't completely manage to make it clear. It has to with the fact that one of the units in the combat already going on is ticking, while the newly arrived unit has not merged yet, but IS in the short-5km-close-enough-for-combat range. Your unit isn't standing still yet, a tick is going on in rangem, and your new unit joins in - and as it is also moving, it becomes an attacker, on a slightly different spot than the to-merge-with unit, so it can't merge quite yet.
That's not the complete story though, as there are exceptions to it as well; apparently it also has to do with the respective exact locations of the units already in combat, and with the angle of approach of the new unit. It all seems to be a bit of a lottery though.
17 Nov 2022, 14:28
Ok, I'm aware of the first "splash damage" issue triggering a "return attack". I suppose I could have just got extremely unlucky multiple times on the enemy tics. In other cases, I may have started marching before I captured the prov so it was still in "attack mode". It would be nice if marching units switched from attacking a prov to just marching to it once the prov is captured. It's the same issue as the march time not being updated.
17 Nov 2022, 15:48
DxC wrote:
Ok, I'm aware of the first "splash damage" issue triggering a "return attack". I suppose I could have just got extremely unlucky multiple times on the enemy tics. In other cases, I may have started marching before I captured the prov so it was still in "attack mode". It would be nice if marching units switched from attacking a prov to just marching to it once the prov is captured. It's the same issue as the march time not being updated.
Marching time and these issues you seem to claim have had 0 effect for me, im not sure if its only me(which it seems to be) but i have never had these problems. marching times are accurate through the captures and then it calculates the speed after those places have been captured, i have no idea at this point.
17 Nov 2022, 16:23
I'm pretty sure travel time and speed not updating until the user does something is universal. When I notice I've captured a province I usually re-order my units or toggle forced march quickly on/off to get the updated travel time and speed numbers for my other stacks that are passing through.
I've experienced the same issue as DxC where sometimes it seems like you've done everything right and yet the reinforcing units still end up attacking. It can be a huge swing in battle outcome when this happens.
One thing I'll note is that I think diplomacy changes also result in a 5km "check" (not sure what to call it). I've noticed that declaring war on someone has resulted in unrelated units immediately taking provinces they were close to taking. Just another thing to avoid doing while you wait for your reinforcements to join up with the defending stack.
17 Nov 2022, 16:32
jubjub bird wrote:
toggle forced march quickly on/off to get the updated travel time
I used to do that but now I click delay then cancel delay for the same result. Although the forced march method probably doesn't consume any HP, my OCD feels better using the delay method.
17 Nov 2022, 16:35
jubjub bird wrote:
I think diplomacy changes also result in a 5km "check"
Yeah, it probably resets/checks status of all your units. I bet it would also update march times.
17 Nov 2022, 16:45
Nice I might have to start trying the delay method. I'm always paranoid that if I don't click off Forced March soon enough I'll lose a tick of health haha
