2020-06-03 15:02 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0006173Spring engineGeneralpublic2019-03-18 11:30
Assigned ToKloot 
PrioritynormalSeverityminorReproducibilityhave not tried
Product Version104.0 +git 
Target VersionFixed in Version104.0 +git 
Summary0006173: 104.0.1-1085-gfc6d80e maintenance Commander avoids building airpad and becomes stuck out of build range
DescriptionIn this game a commander was told to build an air pad. Instead of building the air pad it buggers off in various directions, eventually standing outside of build range and not making any move to get closer. It started happening around 400 3200 6:30. Later the player issued the build order again and the problem was solved.

I disabled luarules at 6:33 (via pause and /skip 393) and the issue still occurred. The command may have been issued while the commander was in MoveCtrl from jumpjets.

TagsNo tags attached.
Checked infolog.txt for ErrorsYes
Attached Files




Kloot (developer)

Last edited: 2019-03-18 00:25

View 3 revisions

This is primarily a unit script bug, it never sets inBuildStance to true.

The bogus bugger-off move orders are issued by Spring which I will handle later.


Google_Frog (reporter)

Is every ZK script using COB.INBUILDSTANCE incorrect? All the scripts I checked set it in script.StartBuilding. https://github.com/ZeroK-RTS/Zero-K/blob/master/scripts/commrecon.lua#L496


Kloot (developer)

I misread some debug output, inBuildStance is being set but the blocker is elsewhere.

-Issue History
Date Modified Username Field Change
2019-03-17 13:11 Google_Frog New Issue
2019-03-17 13:11 Google_Frog File Added: 20190317_222133_Valles_Marineris_v2_104.0.1-1085-gfc6d80e maintenance.sdfz
2019-03-17 13:12 Google_Frog File Added: commAvoidAirpad.jpg
2019-03-18 00:24 Kloot Note Added: 0019873
2019-03-18 00:25 Kloot Note Edited: 0019873 View Revisions
2019-03-18 00:25 Kloot Note Edited: 0019873 View Revisions
2019-03-18 00:26 Kloot Status new => feedback
2019-03-18 01:01 Google_Frog Note Added: 0019874
2019-03-18 01:01 Google_Frog Status feedback => new
2019-03-18 01:48 Kloot Note Added: 0019877
2019-03-18 01:56 Kloot Assigned To => Kloot
2019-03-18 01:56 Kloot Status new => assigned
2019-03-18 11:30 Kloot Status assigned => resolved
2019-03-18 11:30 Kloot Resolution open => fixed
2019-03-18 11:30 Kloot Fixed in Version => 104.0 +git
+Issue History