This bug predates A18. I’ve seen it in at least A17, if not earlier. For a while, I couldn’t quite figure out how to describe it, let alone reproduce it, but I think I finally got it.
When AI paths are long enough AND hearthlings are busy enough at the time, hearthlings will confuse a container that the player has requested to be moved, with a container that’s currently in storage nearby. The hearthling will then place a different empty container where to-be-moved container should have gone. This will result in the to-be-moved container being placed into storage – EVEN IF that container is not empty.
Non-empty containers within other containers has been fixed at least once before, but it appears as though a version of that bug remains unsolved.
Steps to reproduce:
- Load this save (2.7 MB). In it, you’ll find a stone chest that contains 21 stone chests. Inside one of those 21 chests is a chest full of wood.
- Using the place item UI, place stone chests anywhere outside the walls, a few at a time, until the one containing wood has been placed.
- Very deliberately, undeploy EMPTY chests a few at a time until all available hearthlings are actively in the process of hauling a chest.
- Once everyone is actively hauling a chest, instruct your hearthlings to MOVE the chest containing wood to an open space right next to the town flag.
- Observe a different hearthling eventually pull a spare chest out of inventory and plop it down where the wood chest was supposed to go. Once that happens, you’ll see that the wood chest is instead placed into storage.
The wood chest should be placed where instructed, and all empty chests should end up back in storage.
See #5 above
Version Number and Mods in use: