View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0001476 | Spring engine | Unit Scripting | public | 2009-06-28 02:51 | 2009-06-28 02:51 | ||||||||
Reporter | troycheek | ||||||||||||
Assigned To | |||||||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||||||
Status | new | Resolution | open | ||||||||||
Product Version | 0.79.1.0 | ||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0001476: using CMD.REMOVE to remove a command in the queue causes current unit action to stutter | ||||||||||||
Description | Let's say I have a builder who is building something, with several other build orders queued up, and I wish to remove one of the later orders from within my widget. I can do so with Spring.GiveOrderToUnit(unitID, CMD.REMOVE, { cmd.tag }, {} ). However, the builder will stop building then start again each time I do so. Some units take a bit of time to store and redeploy their nanolathes, so this can really add to the build time if remove several orders in rapid succession. I can give the unit the same build order again with Spring.GiveOrderToUnit(unitID, cmd.id, { cmd.params }, { "shift" }) and remove the order without the stutter. | ||||||||||||
Additional Information | Actually product version 0.79.1.2, but didn't see option for that. Tested repeatedly with XTA 9.58 (only mod I have installed at present). | ||||||||||||
Tags | No tags attached. | ||||||||||||
Checked infolog.txt for Errors | |||||||||||||
Attached Files |
|
![]() |
|||
Date Modified | Username | Field | Change |
---|---|---|---|
2009-06-28 02:51 | troycheek | New Issue |