| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0003293 | Spring engine | Lua | public | 2012-10-02 18:04 | 2012-10-06 14:18 | ||||
| Reporter | sprung | ||||||||
| Assigned To | Kloot | ||||||||
| Priority | low | Severity | trivial | Reproducibility | always | ||||
| Status | resolved | Resolution | fixed | ||||||
| Product Version | 91.0 | ||||||||
| Target Version | Fixed in Version | 91.0.1+git | |||||||
| Summary | 0003293: Spring.GetUnitNearestAlly takes self into account | ||||||||
| Description | Spring.GetUnitNearestAlly takes self into account, so it returns the unitID passed into the function. While the unit's closest allied unit is indeed itself, I doubt this is the desired behaviour. | ||||||||
| Steps To Reproduce | Umm, call Spring.GetUnitNearestAlly ? | ||||||||
| Tags | No tags attached. | ||||||||
| Checked infolog.txt for Errors | |||||||||
| Attached Files |
| ||||||||
 Relationships |
|
 Relationships |
| Notes |
|
| There are no notes attached to this issue. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-10-02 18:04 | sprung | New Issue | |
| 2012-10-06 14:18 | Kloot | Status | new => resolved |
| 2012-10-06 14:18 | Kloot | Fixed in Version | => 91.0.1+git |
| 2012-10-06 14:18 | Kloot | Resolution | open => fixed |
| 2012-10-06 14:18 | Kloot | Assigned To | => Kloot |
| Issue History |