| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0003069 | Spring engine | General | public | 2012-04-21 03:53 | 2012-04-21 11:16 |
|
| Reporter | klapmongool | |
| Assigned To | Kloot | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | |
| Product Version | 88.0 | |
| Target Version | | Fixed in Version | 89.0 | |
|
| Summary | 0003069: Con/com gets weird move order after stop command is given |
| Description | When a constructor or commander is assisting or building (standing still) and it is given a stop order (for example in order to set up a new build queue) it receives a move order from the engine. It is not a normal move order as the unit will normally not complete it. It seems as if this move order is given because spring thinks the unit is too close to a building. Replay in which issue is reproduced included.
Impact: Happens dozens of times per game and is very annoying when giving new orders to cons/com after assisting a lab because they tend to walk in to the location of the newly given build order.
|
| Additional Information | http://springrts.com/phpbb/viewtopic.php?f=44&t=28066 [^] |
| Tags | No tags attached. |
|
| Attached Files |  20120421_085506_Comet Catcher Redux_88.sdf [^] (25,459 bytes) 2012-04-21 03:53 |
|
Relationships 
Relationships