2025-07-16 09:32 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0003012Spring engineGeneralpublic2012-03-13 21:58
ReporterGoogle_Frog 
Assigned Toabma 
PrioritynormalSeverityblockReproducibilityalways
StatusresolvedResolutionduplicate 
Product Version87.0.1+git 
Target VersionFixed in Version 
Summary0003012: Builders stop area commands when no wrecks are in range
DescriptionWhich version is this supposed to be fixed in? It is still broken in 87.0.1-15-gbf0b94c.

Also I cannot reopen other people's tickets.
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files
  • jpg file icon bug1.JPG (178,087 bytes) 2012-03-13 20:51 -
    jpg file icon bug1.JPG (178,087 bytes) 2012-03-13 20:51 +

-Relationships
duplicate of 0003004closed builders stop area reclaim 
+Relationships

-Notes

~0008433

Kloot (developer)

Last edited: 2012-03-13 13:21

Why wouldn't builders stop "area commands" (you obviously mean reclaim here, learn to be specific) when NO wrecks are "in range"? _WHAT_ range, command radius or reclaim radius? _WHAT_ aspect of this is different than in 85? Illustrate with demos, not words.

~0008434

Google_Frog (reporter)

I thought the context was clear because of the related bug which you recently said you fixed. This report was along the lines of a reopening. http://springrts.com/mantis/view.php?id=3004

Here is the replay of a full game test for the new engine. http://zero-k.info/Battles/Detail/60058

At 580, 270 3:25 a Rector has a reclaim area reclaim order that is inactive due to this bug.

At 590, 1540 4:38 the same Rector has a fight command and is inactive again with a queued reclaim order.

~0008436

Kloot (developer)

Last edited: 2012-03-13 14:21

"Engine version: 87.0" ...?

The demo's filename also indicates this was not a development build.

~0008439

djmad (reporter)

Last edited: 2012-03-13 21:12

the problem with waypointfinder also accures at BA7.64

areacommand reclaim or resurrect

the unit is standing still an does not go to the next point where its able to resurrect/repair/reclaim the next unit/wreck
it seems the unit does not get a new movingtarget, when aiming at a wreck out of range

there is a screenshot uploaded by me, where u can see the situation,
the con has the mission to reclaim everything, did the first 5 wrecks in range, then started moving for around 2mm on my screen, stoppend and started to aim at the wreck, but does not move in range for using its tools

All Widgets off

This happens not to planes, maybe the waypoint-finder has some problems

~0008442

abma (administrator)

@djmad:
this has been already fixed in the development version with this commit:

https://github.com/spring/spring/commit/976d7739adb2ce268f16d8f0cb022476ee5d7e61

(also "closed" tickets can't be reopened for reason, "resolved" tickets can be reopened)

if you want to test, use the latest installer: http://springrts.com/dl/buildbot/default/develop/spring_testing.exe (note, with this version you can't play online!)

see also 0003004


@kloot:

cool down, i see just a nervous gamer here :) (also, i love your pathfinder changes, really, its really good now. sadly users still don't see / recognize because of minor bugs)
+Notes

-Issue History
Date Modified Username Field Change
2012-03-13 06:53 Google_Frog New Issue
2012-03-13 13:19 Kloot Note Added: 0008433
2012-03-13 13:21 Kloot Note Edited: 0008433
2012-03-13 13:31 Google_Frog Note Added: 0008434
2012-03-13 14:16 Kloot Note Added: 0008436
2012-03-13 14:20 Kloot Note Edited: 0008436
2012-03-13 14:21 Kloot Note Edited: 0008436
2012-03-13 20:51 djmad Note Added: 0008439
2012-03-13 20:51 djmad File Added: bug1.JPG
2012-03-13 20:53 djmad Note Edited: 0008439
2012-03-13 21:12 djmad Note Edited: 0008439
2012-03-13 21:12 djmad Note Edited: 0008439
2012-03-13 21:58 abma Note Added: 0008442
2012-03-13 21:58 abma Relationship added duplicate of 0003004
2012-03-13 21:58 abma Duplicate ID 0 => 3004
2012-03-13 21:58 abma Status new => resolved
2012-03-13 21:58 abma Resolution open => duplicate
2012-03-13 21:58 abma Assigned To => abma
+Issue History