Going Medieval update 10 (0.16.24) is rolling out on PC. According to the official Going Medieval patch notes, the latest update addresses various bugs and implementing quality of life improvements.
Previously, a major Going Medieval update added new changes, fixes, and gameplay improvements. Unfortunately, players are still experiencing several issues since the release. Today’s Going Medieval patch 0.16.24 will fix a few of these issues.
Check out more details below.
Going Medieval 0.16.24 Patch Notes – March 6, 2024
Bugs and Fixes
- Fixed the issue where settlers and animals ended up stuck in water upon their caravan return.
- Fixed the issue where settlers would suddenly get stuck in high + low water and were drowning as a result.
- Fixed the issue where settlers were not able to pick up piles that were located on the edge between shallow and deep water.
- Fixed the issue where the settler would in some cases end up stuck in a constructing goal loop and never completing the task.
- Fixed the issue where settlers would never go to sleep if it was raining and there was no cover present and beds were unavailable.
- Fixed the issue where settlers would try to bring resources to production building, but suddenly stopping and dropping resources and repeating the whole process.
- Fixed the issue where upon loading the game, “hide tree top” function would be active, but in the UI it would appear as disabled and the trees would be fully visible. This would cause an appearance of trees not being selectable.
Quality of life improvements
- Production circle would remain blue even when it has all of the necessary resources in it. It will turn yellow only when settlers start using a production building.
Present frustrating issues:
- If settlers end up stuck, ignoring jobs (that are properly set and scheduled), and not behaving as intended, consider saving & reloading the game as there is a big chance that it may fix the issue.
- It seems that the situation where you try to build a soil voxel and it crumbles upon completed construction still happens. As with the issue above, it’s close to impossible to reproduce this issue on our side. We’re working on a potential memory fix that may, in turn, solve this issue and some other stuff. In the meantime, if you encounter this bug, please provide as much info/context as possible. Quitting the game and starting the save will solve the issue.
