2025-07-18 04:17 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0002989Spring engineGeneralpublic2012-03-09 14:25
ReporterGoogle_Frog 
Assigned ToKloot 
PrioritynormalSeveritymajorReproducibilityalways
StatusresolvedResolutionfixed 
Product Version86.0 
Target VersionFixed in Version87.0.1+git 
Summary0002989: Units can be built on impassable terrain.
DescriptionUnits can be placed by constructors such that they will be stuck on terrain when completed. The units have equal maxslope in unitdef and movedef so I would expect even placement. If the two differnt maxslopes are not actually meant to correspond there should be something else that does correspond.

Construction placement is not a large issue because players have to go out of their way to break it. The much larger issue is that Spring.TestBuildOrder and this affects many gadget. Spring.TestBuildOrder is currently used for things such as jumpjet and teleportation destination checking. Now jumpjetted units can become stuck in terrain which to me is a greater problem.
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0008370

Kloot (developer)

Last edited: 2012-03-01 02:12

"Spring.TestBuildOrder is currently used for things such as jumpjet and teleportation destination checking."

Then your gadgets are broken to begin with.

The fact a separation exists between MoveDefs and UnitDefs should make it extremely obvious that where a unit can move != where a unit can be built in the general case, slope tolerance is NOT the only factor.

"Now jumpjetted units can become stuck in terrain which to me is a greater problem."

And why is checking the destination of a jump not the user's problem? If I tell a Can to jump off a cliff into water where F2 clearly shows it cannot normally move, are you going to blame TestBuildOrder for that?

~0008371

Google_Frog (reporter)

That is a poor UI. If Spring.TestBuildOrder is not meant for this (even though the tags have the same names) then I request another function that tests whether a mobile unit will be stuck at a location.
+Notes

-Issue History
Date Modified Username Field Change
2012-02-29 17:16 Google_Frog New Issue
2012-02-29 17:16 Google_Frog File Added: screen00241.png
2012-02-29 17:18 Google_Frog File Added: screen00242.png
2012-03-01 02:11 Kloot Note Added: 0008370
2012-03-01 02:12 Kloot Note Edited: 0008370
2012-03-01 08:08 Google_Frog Note Added: 0008371
2012-03-09 14:25 Kloot Status new => resolved
2012-03-09 14:25 Kloot Fixed in Version => 87.0.1+git
2012-03-09 14:25 Kloot Resolution open => fixed
2012-03-09 14:25 Kloot Assigned To => Kloot
+Issue History