Commander walks to the enemy while ordered to assist

[JoonasTo]

Ordered a commander to assist a loading tml(no target yet), it started walking straight to the enemy. Assist ground or assist directly, no matter.
#4721233

Also seen this happen when assisting an upgrading mex on setons front by Jazzi.
#4717941

[nine2]

i've had some odd things happening too.

[Crotalus]

Yeah the ACU was guarding (assist) the tml structure and then saw enemies within range and thought it was a good idea walking there killing it, i.e. guarding the structure from enemies.

Without having tested it, maybe it would have been different if tml was building a missile due to possible being priortized higher than "kill enemies in range" (but the Jazzi case would be a counter-argument to that).

Maybe the recent changes with GuardScanRadius impacts this as well, I don't know what the ACUs default range was earlier before we changed it to weapon range.

[Crotalus]

Yeah, assisting something that actually builds something results in the same thing, the ACU still wants to attack an enemy within it's range.

[Hawkei]

Assist is a very generalised command. The unit itself determines the manner of assistance it will give. The assist command forces combat units to stay within a certain distance of the target unit. Scouts, and spy planes when told to "assist" an enemy, with fly in circles overhead. Or ASF when told to assist the ground, or a stealth generator, will fly overhead in a tight circle. Ready to ambush anything flying nearby. Transports when told to assist a factory, will aid it by loading units, and delivering them to the designated waypoint.


Assist is a very versatile command, and doesn't simply mean the application of build power. The ACU, being also a combat unit, will assign higher priority to attacking nearby enemies. Once the enemies are killed it will resume the build assist function.

[nine2]

Hawkei whilst you are no doubt right ... Wtf... He is talking about his acu walking across half the map which is clearly new, a bug, and suicidal.

[IceDreamer]

No, this is a mistake of the GuardScanRadius stuff, which previously defaulted to 26, just a bit more than an ACU's normal range. This behaviour was always a thing for units inside that. A few patches back, things were changed so GSR was dynamically generated at launch based on your unit's highest range weapon, in the case of some ACUs, the TML, or Torpedo launcher etc.

Solution: Hard-code ACU and sACU GSR to 30 (Range of upgraded cannon) or 22 (Default range).

[nine2]

Well then other units will assist and walk in.
Find something special about tml weapons and don't inherit their radius?

[Crotalus]

TML should already be excluded from GSR due to being a CountedProjectile, so the GuardScanRadius for ACU are probably around 30:ish.

[IceDreamer]

I've logged it. The current GSR values for the ACUs are as follows:


UEF - 31.4999
Cybran - 69
Aeon - 36.75
Seraphim - 31.4999

Aeon's larger one is thanks to the larger range on the gun upgrade. The Cybran's is the Torpedo Launcher, which is counted by the system.

My recommendation remains the same: We can avoid undue complexity with trying to filter out the Torpedo Launcher for just the ACU by simply hard-coding it into the unit blueprint for ACUs and sACUs.