It’s still there in at least some forms. See my post here.
I’m getting this a lot on my home machine (I play at work sometimes… ssshhhh!). Home machine is geared for gaming, and so far it’s the only place I am seeing it.
In the log it looks like it might be tied to the presence (or attempted presence) of a goblin raiding party. I found this in the log right after loading a bad save:
-21 20:02:40.726826 | 0 | lua.code | -- Script Error (lua) Begin -------------------------------
2014-Aug-21 20:02:40.726826 | 0 | lua.code | radiant/lib/env.lua:6: assertion failed!
2014-Aug-21 20:02:40.726826 | 0 | lua.code | stack traceback:
2014-Aug-21 20:02:40.726826 | 0 | lua.code | [C]: ?
2014-Aug-21 20:02:40.726826 | 0 | lua.code | [C]: in function 'old_assert'
2014-Aug-21 20:02:40.727826 | 0 | lua.code | radiant/lib/env.lua:6: in function 'assert'
2014-Aug-21 20:02:40.727826 | 0 | lua.code | radiant/modules/events.lua:43: in function 'listen'
2014-Aug-21 20:02:40.727826 | 0 | lua.code | radiant/modules/events.lua:29: in function 'listen_once'
2014-Aug-21 20:02:40.727826 | 0 | lua.code | ...h/scenarios/dynamic/goblin_brigands/escort_squad.lua:126: in function '_attach_listeners'
2014-Aug-21 20:02:40.727826 | 0 | lua.code | ...h/scenarios/dynamic/goblin_brigands/escort_squad.lua:15: in function '__user_init'
2014-Aug-21 20:02:40.727826 | 0 | lua.code | radiant/lualibs/unclasslib.lua:276: in function '__init'
2014-Aug-21 20:02:40.727826 | 0 | lua.code | radiant/lualibs/unclasslib.lua:207: in function 'EscortSquad'
2014-Aug-21 20:02:40.727826 | 0 | lua.code | ...cenarios/dynamic/goblin_brigands/goblin_brigands.lua:25: in function 'obj'
2014-Aug-21 20:02:40.727826 | 0 | lua.code | radiant/modules/events.lua:33: in function 'self'
2014-Aug-21 20:02:40.727826 | 0 | lua.code | radiant/modules/events.lua:174: in function <radiant/modules/events.lua:141>
2014-Aug-21 20:02:40.727826 | 0 | lua.code | -- Lua Error End -------------------------------
The only thing that makes me suspect it might be tied to goblin shenanigans is the randomness, given the quirksome behavior we’ve all seen the past couple of days with them.
Summary:
Upon reloading a saved game, all non-worker classed villagers (Trappers, Farmers, Carpenters, Footman, etc.) are found partially buried in the ground with only their head visible. These villagers are no longer functional, and cannot move or perform tasks of any kind.
Reloading the save does not fix the problem, and no workable solution is visible.
Steps to reproduce:
I’m unsure whether or not this had anything to do with it, but I had recieved a new villager as a Footman and the game threw an LUA error. The Footman did not show up on my list of villagers even as he patrolled through my town and selecting anything did not display it’s listed name in the bottom-left corner of the screen. It’s then when I saved and reloaded. With this in mind, the steps to replicate are:
- Receive new villager (possibly of a class other than base worker)
- Save game
- Reload game
Expected Results:
Properly reloaded game with functioning villagers.
Actual Results:
All non-worker villagers (half population) rendered useless.
Notes:
Again, I’m not sure if the two errors are related, or perhaps it was the fact the game was saved after an error was thrown about the new recruit to the village.
Attachments:
Can upload save file upon request
Versions and Mods:
I’m running Stonehearth v0.1.0 (release 122), Alpha 4.
System Information:
Windows 7 Professional 64 | AMD fx 8350 Eight-Core Processor ~4GHz | 8GB RAM | Radeon HD 7970
I think this has been mentioned before, and is a bug that was here since the last release of A4.
Apologies if it has. I found nothing using the search function. Should I remove my thread?
no worries! your thread has been merged with the original report… 
I’m also experiencing this problem of the villagers being sunk, stuck in the ground. Is there any fix, or is the only option at the moment to restart the game?
Start a new game is the only fix I know of.
This still happens.