| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0003172 | Spring engine | General | public | 2012-07-11 20:14 | 2012-07-12 02:41 | ||||
| Reporter | Beherith | ||||||||
| Assigned To | Kloot | ||||||||
| Priority | normal | Severity | major | Reproducibility | always | ||||
| Status | resolved | Resolution | fixed | ||||||
| Product Version | 89.0 | ||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0003172: 89: Lock on target of units results in them not firing at anything else if they move out of range | ||||||||
| Description | I love the new lock on target feature of units retaining their target after getting a move order, but it has some small issues: 1. If a unit is ordered to attack ground, it wont stop until it is given a stop command. This is an acceptable side effect. 2. If a unit is ordered to attack another unit, and the target goes out of range, the unit stops aiming and shooting at any other unit. This is highly undesirable. 3. There is no visual indication that a unit is locked on a target, and actively tries to aquire said target if it doesnt have any other commands. | ||||||||
| Tags | No tags attached. | ||||||||
| Checked infolog.txt for Errors | |||||||||
| Attached Files |
| ||||||||
 Relationships |
|
 Relationships |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-07-11 20:14 | Beherith | New Issue | |
| 2012-07-12 02:41 | Kloot | Note Added: 0008954 | |
| 2012-07-12 02:41 | Kloot | Status | new => resolved |
| 2012-07-12 02:41 | Kloot | Resolution | open => fixed |
| 2012-07-12 02:41 | Kloot | Assigned To | => Kloot |
| Issue History |