2024-04-18 19:06 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0004850Spring engineGeneralpublic2015-07-01 14:26
ReporterGoogle_Frog 
Assigned Tohokomoko 
PrioritynormalSeveritymajorReproducibilitysometimes
StatusresolvedResolutionfixed 
Product Version99.0+git 
Target VersionFixed in Version 
Summary0004850: 99.0.1-20 Gunship Jitter
DescriptionIn this replay at around 28:05 5800 1300 a gunship is trying to attack but becomes stuck jittering just outside its attack range. The units trying to fire at the gunship fire in front of the gunship, missing it, because it has high velocity but the jittering causes it to stay in one spot.
Steps To ReproduceSpawn 20 battledrone and give them a fight order towards an enemy factorycloak. Some of them should jitter just outside attack range.
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0014732

Google_Frog (reporter)

Link because Mantis fails at file size http://zero-k.info/Battles/Detail/361114

~0014811

hokomoko (developer)

Fix 9d1b5acbba6a94514909823fea846a6f733448d2 committed to develop branch: Another attempt to try and Fix 0004850, repo: spring changeset id: 5280

~0014812

hokomoko (developer)

GoogleFrog can you test general gunship behaviour in 99.0.1-41-g9d1b5ac?

~0014816

Google_Frog (reporter)

Gunships seemed to work but I have not done a lot of testing.
+Notes

-Issue History
Date Modified Username Field Change
2015-06-27 16:09 Google_Frog New Issue
2015-06-27 16:53 Google_Frog Note Added: 0014732
2015-07-01 00:45 hokomoko Changeset attached => spring develop 9d1b5acb
2015-07-01 00:45 hokomoko Note Added: 0014811
2015-07-01 00:45 hokomoko Assigned To => hokomoko
2015-07-01 00:45 hokomoko Status new => resolved
2015-07-01 00:45 hokomoko Resolution open => fixed
2015-07-01 00:45 hokomoko Status resolved => feedback
2015-07-01 00:45 hokomoko Resolution fixed => reopened
2015-07-01 01:01 hokomoko Note Added: 0014812
2015-07-01 05:15 Google_Frog Note Added: 0014816
2015-07-01 05:15 Google_Frog Status feedback => assigned
2015-07-01 14:26 hokomoko Status assigned => resolved
2015-07-01 14:26 hokomoko Resolution reopened => fixed
+Issue History