So, for you in the latest version, the maintain option is still bugged…
Thanks for the report / confirmation!
This is Alpha 10.5 from Steam. And just to clarify, the Comfy Bed seems to be the only item I am having this problem with. So far all Maintain orders for other items has worked as expected.
However, for all other items it seems to have a problem with sometimes producing one extra. It is not consistent which items produce extra, but for these other items, it is only ever 1 extra.
I have noticed this - I think the reason is that the total town inventory doesn’t instantly update. So, let’s say you have “maintain 5 mean beds” for your carpenter. You have 4 in the stockpile, then this happens:
- The carpenter finishes crafting the 5th bed.
- The carpenter places the 5th bed in the stockpile.
- The carpenter checks the town inventory, finds only 4 beds, and starts work on another one.
- The stockpile registers the 5th bed being placed, and updates the town inventory.
- The carpenter finishes what’s now the 6th bed.
- The carpenter places the 6th bed.
It all has to do with how the listeners line up, and the fact that sometimes steps 3 and 4 are reversed (which would make them correct).
For this reason, anything that requires the worker to craft another item first (say, the blacksmith making another steel ingot before crafting another trapper’s knife) works correctly, since the stockpiles update before the new item (steel ingot, in this case) is finished.
We are finally, finally fixing this, as part of overhauling what things count as being “in your inventory.” Fingers crossed.
When i tell my carpenter to maintain 1 wooden shield, he/she often keeps 2 in the stockpile…
This is in build 375.
It happens on almost all maps…
hmm… yes this has been reported before, that the “maintain x amount in stockpile” is broken.
But with a practice wooden sword it seems fine… Maybe i haven’t noticed it.
well from the reports ive seen, only certain items have the problem, mainly beds and other furniture.
So yeah, it’s still in R393, but since @sdee said the team was working on it, it’ll probably be fixed for Alpha 11… hopefully. So… yeah… probably fine to ignore this message
25:34