2025-07-22 06:36 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0003835Spring engineGeneralpublic2013-08-11 01:13
ReporterGoogle_Frog 
Assigned ToKloot 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
Product Version94.1.1+git 
Target VersionFixed in Version94.1.1+git 
Summary0003835: Units give themselves attack orders, do not obey weapon target priorities
DescriptionThe attack commands automatically given to a unit on hold position do not obey target priority as set with gadget:AllowWeaponTarget. Worse, the priority set fights with the attack commands.

In this battle the Slasher idles and receives attack commands. AllowWeaponTarget tells it to shoot at the Lotus but it's attack command is telling it to shoot at the nearest enemy. The target priority will fight the attack command and cause the weapon to fiddle around and sometimes shoot the Lotus.
http://zero-k.info/Battles/Detail/172239

In this battle the Slasher is given a repeat move order to a point. This prevents it from automatically gaining attack commands. The Slasher fires at the high priority targets correctly.
http://zero-k.info/Battles/Detail/172242

The simplest solution I can think of is for units to not automatically receive attack orders when idling on hold position. Although iirc S44 needs this behaviour to make their infantry rotate so it would be best if a unit tag could control whether units receive attack commands in this way. The best solution would be if the automatically given attack commands obeyed weapon (primary I suppose) target priority.
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0011275

Kloot (developer)

Changed so weapon- and command-AI will no longer clash.

There is much to be improved about the auto-generated attack orders but that can wait.
+Notes

-Issue History
Date Modified Username Field Change
2013-06-04 12:50 Google_Frog New Issue
2013-08-11 01:13 Kloot Note Added: 0011275
2013-08-11 01:13 Kloot Status new => resolved
2013-08-11 01:13 Kloot Fixed in Version => 94.1.1+git
2013-08-11 01:13 Kloot Resolution open => fixed
2013-08-11 01:13 Kloot Assigned To => Kloot
+Issue History