View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
---|---|---|---|---|---|---|---|---|---|
0003450 | Spring engine | Lua | public | 2013-02-08 20:30 | 2017-09-14 22:14 | ||||
Reporter | nixtux | ||||||||
Assigned To | |||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||
Status | closed | Resolution | reopened | ||||||
Product Version | 91.0 | ||||||||
Target Version | Fixed in Version | 103.0 +git | |||||||
Summary | 0003450: Spring.SetUnitBuildSpeed setting a value of 0 does not stop reclaim | ||||||||
Description | tested with Spring 91.0.1-1321-gc19898c and as above setting Spring.SetUnitBuildSpeed(unitID, 170,0,0) third value to 0 does not stop a unit from reclaiming , unlike repair which does stop | ||||||||
Tags | No tags attached. | ||||||||
Checked infolog.txt for Errors | |||||||||
Attached Files |
|
![]() |
|
nixtux (reporter) 2013-02-18 11:51 |
Add link to for gadget to reproduce this bug https://github.com/n3wm1nd/TA/blob/master/luarules/gadgets/unit_nanoboost.lua |
hokomoko (developer) 2016-11-05 21:03 |
Can you please test if Spring.SetUnitBuildSpeed(unitID, 170,0,0,0) works with 103.0 or later? |
nixtux (reporter) 2017-09-14 20:39 |
Just tested with latest techa + engine 103.0.1-1381-g2887f3d4b, with reclaim speed set to 0 with setunitbuildspeed and builders can still reclaim Steps to reproduce Use latest techa, start game /give 1 armnanotc, set nano to boosts mode, give 1 armstump_dead, bingo nano will reclaim wreak |
nixtux (reporter) 2017-09-14 20:45 |
Ohh btw techa repo moved its now here if you need it https://github.com/techannihilation/TA |
Kloot (developer) 2017-09-14 22:09 Last edited: 2017-09-14 22:13 |
this is a case of "fix your Lua code first". if I modify TA's unit_nanoboost.lua s.t. it calls Spring.SendCommands("luarules disable") right after Spring.SetUnitBuildSpeed(unitID, buildspeedlist[unitID].speed * 1.8, 0, 0) the reclaim is stopped (order persists, but makes no further progress) so some gadget is ultimately responsible for continuing to remove resources, and I'm going to guess that would be unit_reclaim_fix which happens to contain a Spring.SetFeatureReclaim call. |
![]() |
|||
Date Modified | Username | Field | Change |
---|---|---|---|
2013-02-08 20:30 | nixtux | New Issue | |
2013-02-18 11:51 | nixtux | Note Added: 0009842 | |
2016-11-05 21:03 | hokomoko | Note Added: 0016850 | |
2016-11-05 21:03 | hokomoko | Assigned To | => hokomoko |
2016-11-05 21:03 | hokomoko | Status | new => feedback |
2017-09-14 08:00 | hokomoko | Status | feedback => closed |
2017-09-14 08:00 | hokomoko | Resolution | open => unable to reproduce |
2017-09-14 20:39 | nixtux | Status | closed => feedback |
2017-09-14 20:39 | nixtux | Resolution | unable to reproduce => reopened |
2017-09-14 20:39 | nixtux | Note Added: 0018392 | |
2017-09-14 20:45 | nixtux | Note Added: 0018393 | |
2017-09-14 20:45 | nixtux | Status | feedback => assigned |
2017-09-14 22:09 | Kloot | Note Added: 0018394 | |
2017-09-14 22:13 | Kloot | Note Edited: 0018394 | View Revisions |
2017-09-14 22:14 | Kloot | Assigned To | hokomoko => |
2017-09-14 22:14 | Kloot | Status | assigned => closed |
2017-09-14 22:14 | Kloot | Fixed in Version | => 103.0 +git |