It happened to me when my workers were building a window, but I think this wasn’t for that, jus saying that was the last thing I saw before this:
You can close the window but reappears over and over again. The red number in the top left corner was growing up too.
since i am a new user i can not upload my screen shots. Its an Engine error, first 3 minutes of gameplay i got 5000 errors.
the first line says: stonehearth/components/ai/execution_frame.luac:653: stonehearth/components/ai/execution_frame.luac:653: stonehearth/components/ai/execution_frame.luac:653: stonehearth/components/ai/execution_frame.luac:653: stonehearth/ai/filters/teardown_wooden_structure_filter.luac:4: bad argument #1 to ‘find’ (string expected, got nil)
out of all the 5000 errors most of them mention “teardown_wooden_structure_filter.luac:4: bad argument #1 to ‘find’ (string expected, got nil)”
Hello there,
Just to let you know that I got this error too, I do as @Wiese2007 said but it did not fix anything.
I have copied my saved_games and saved_object folders and deleted stonehearth fully from SteamApps/common/, then redownloading the game, and then paste my saved_games and saved_object in SteamApps/common/HearthStone.
Sadly, it did not fix anything…
I have tried to watch the log and I noticed that the error is always the same, I assume that it happened in some event loop (Yes I am a programmer too 
) involving the ai but i did not get all. Anyway here is the 3 same errors log lines that always appears 5 seconds after I load any saved games.
2015-Jun-10 23:25:14.367677 | server | 0 | lua.code | -- Script Error (lua) Begin -------------------------------
2015-Jun-10 23:25:14.367677 | server | 0 | lua.code | stonehearth/components/ai/execution_frame.luac:653: stonehearth/components/ai/execution_frame.luac:653: stonehearth/components/ai/execution_frame.luac:653: stonehearth/components/ai/execution_frame.luac:653: ...rth/ai/filters/teardown_wooden_structure_filter.luac:4: bad argument #1 to 'find' (string expected, got nil)
2015-Jun-10 23:25:14.367677 | server | 0 | lua.code | stack traceback:
2015-Jun-10 23:25:14.367677 | server | 0 | lua.code | stonehearth/components/ai/execution_frame.luac:637: in function <stonehearth/components/ai/execution_frame.luac:630>
2015-Jun-10 23:25:14.367677 | server | 0 | lua.code | [C]: in function 'error'
2015-Jun-10 23:25:14.367677 | server | 0 | lua.code | stonehearth/components/ai/execution_frame.luac:653: in function '_exit_protected_call'
2015-Jun-10 23:25:14.367677 | server | 0 | lua.code | stonehearth/components/ai/execution_frame.luac:648: in function '_protected_call'
2015-Jun-10 23:25:14.367677 | server | 0 | lua.code | stonehearth/components/ai/execution_frame.luac:324: in function 'run'
2015-Jun-10 23:25:14.367677 | server | 0 | lua.code | stonehearth/components/ai/execution_unit_v2.luac:269: in function '?'
2015-Jun-10 23:25:14.367677 | server | 0 | lua.code | stonehearth/components/ai/execution_unit_v2.luac:12: in function 'execute'
2015-Jun-10 23:25:14.367677 | server | 0 | lua.code | stonehearth/ai/actions/idle_action.luac:8: in function 'call_fn'
2015-Jun-10 23:25:14.367677 | server | 0 | lua.code | stonehearth/components/ai/execution_unit_v2.luac:16: in function '_call_run'
2015-Jun-10 23:25:14.367677 | server | 0 | lua.code | stonehearth/components/ai/execution_unit_v2.luac:174: in function '_run_from_started'
2015-Jun-10 23:25:14.367677 | server | 0 | lua.code | stonehearth/components/ai/execution_unit_v2.luac:115: in function '_run'
2015-Jun-10 23:25:14.367677 | server | 0 | lua.code | ...
2015-Jun-10 23:25:14.367677 | server | 0 | lua.code | stonehearth/components/ai/execution_frame.luac:82: in function '_run'
2015-Jun-10 23:25:14.367677 | server | 0 | lua.code | stonehearth/components/ai/execution_frame.luac:322: in function <stonehearth/components/ai/execution_frame.luac:316>
2015-Jun-10 23:25:14.368677 | server | 0 | lua.code | [C]: in function 'xpcall'
2015-Jun-10 23:25:14.368677 | server | 0 | lua.code | stonehearth/components/ai/execution_frame.luac:639: in function '_protected_call'
2015-Jun-10 23:25:14.368677 | server | 0 | lua.code | stonehearth/components/ai/execution_frame.luac:324: in function 'run'
2015-Jun-10 23:25:14.368677 | server | 0 | lua.code | stonehearth/components/ai/ai_component.luac:118: in function '_thread_main'
2015-Jun-10 23:25:14.368677 | server | 0 | lua.code | stonehearth/services/server/threads/thread.luac:90: in function <stonehearth/services/server/threads/thread.luac:89>
2015-Jun-10 23:25:14.368677 | server | 0 | lua.code | [C]: in function 'xpcall'
2015-Jun-10 23:25:14.368677 | server | 0 | lua.code | stonehearth/services/server/threads/thread.luac:89: in function 'f'
2015-Jun-10 23:25:14.368677 | server | 0 | lua.code | radiant/lib/env.luac:8: in function <radiant/lib/env.luac:8>
2015-Jun-10 23:25:14.368677 | server | 0 | lua.code | -- Lua Error End -------------------------------
Edit : I’m on Last steam release 393 x64
well the reason the problem didnt “resolve” may be due to the fact you kept the saved_games and saved_objects folders, they may have been corrupted.
I was expecting someone to say that, but what I don’t understand is how it append on all the saves.
Before I reinstall everything, I got 3 saves of the same world, the auto-save and 2 others, I was playing and suddenly lua take 70% of cpu with these errors. So I quit the game (alt-F4, not really properly but can’t do anything else) and reload the auto-save. Same events happen 5 second after launching the game, and the result is the same for the 2 others saves that was 1 or 2 game days before my crash…
I will try to launch a new world to see if this also happen.
I tested 5 minutes with a new game and it did not do any errors
I bought the game yesterday and love the concept. The polish is real, and the AI seems good, when it works anyway.
I know it’s a well known trend, the massive number of error messages the game generates. But I thought I’d give a more specific case.
Any time I try to delete even one object from a design, I get a wall of errors, the frame rate drops to 1, and I crash to desktop.
Screenshot can’t be provided, as I am a new user.
It’s a shame. To truely enjoy this game you currently have to learn a lot of workarounds for bugs at first. Doesn’t make the core of the game less fun I have to say. Let’s keep in mind this is an Alpha.
When it come to LUA the game definitely needs some work. I get LUA errors when doing the same thing, but it’s never caused my client to crash. I do notice the same issues of the game slowing down depending on the errors though.
Are there any workarounds? I can’t find any.
@rusinylancer - Welcome to the forum! To be more specific, are you hitting undo on a building while designing it and are getting lua errors?
The errors are not due to use of the undo button (although that button is pretty buggy as well, it’s not the topic).
Typically, I will get a flood of Lua errors upon editting an already constructed building, or upon deleting blocks during design via the eraser tool.
(I can post screenshots now, hooray!)
this isnt necessarily something you should be doing 
Yeah, these errors appears just after I order to remove an unfinished wall.
well currently editing buildings that are under construction or already completed, will cause errors, so for now you just have to do the editing while its still a blueprint.
Slight derailment, but since nobody seems to have done it yet, Welcome, @Nathan_rodz, to Discourse!
Ok, this should be fixed for the next release. Thanks for the reports!
Thanks ! I can’t wait for the next release, I’ve broken another save 
