release-689 (x64)
stonehearth/services/server/ai/ai_service.lua:379: placeholder PREV.item failed to return a value in “compound: heal entity” action
stack traceback:
[C]: in function 'error’
stonehearth/services/server/ai/ai_service.lua:379: in function <stonehearth/services/server/ai/ai_service.lua:373>
[C]: in function 'fn’
stonehearth/services/server/threads/thread.lua:346: in function 'private_msg’
stonehearth/services/server/threads/thread.lua:543: in function '_dispatch_messages’
stonehearth/services/server/threads/thread.lua:403: in function <stonehearth/services/server/threads/thread.lua:384>
[C]: in function 'suspend’
stonehearth/ai/actions/run_effect_action.lua:79: in function <stonehearth/ai/actions/run_effect_action.lua:38>
[C]: ?
[C]: ?
[C]: in function ‘execute’
…
[C]: in function 'run’
stonehearth/components/ai/ai_component.lua:555: in function <stonehearth/components/ai/ai_component.lua:539>
[C]: in function 'xpcall’
radiant/modules/common.lua:257: in function 'xpcall’
stonehearth/components/ai/ai_component.lua:539: in function '_thread_main’
stonehearth/services/server/threads/thread.lua:273: in function <stonehearth/services/server/threads/thread.lua:270>
[C]: in function 'xpcall’
radiant/modules/common.lua:257: in function 'xpcall’
stonehearth/services/server/threads/thread.lua:270: in function 'f’
radiant/lib/env.lua:15: in function <radiant/lib/env.lua:14>
Once you accumulate too many bugs, there is little you can do. Even simple tasks starts raising errors. Checking the previous messages you had a fair amount of errors already…
Try to save your templates so at least the time you invested designing them is not lost, so it can be redone in the next world.
I’m still around the block folks! Just been messing with stonehearth a lot in my off air time. Need to make a stream block for it again Had quite a bit of fun with the newest alpha on the latest build. Seeing a lot of improvements but one this has me worried. Do they use their road maps anymore? The on site road map and community road maps seem to be all but abandoned. @8BitCrab
the team definitely has a clear plan of what they’re doing, if that’s why you’re concerned, as for the why on it not getting updated for awhile check this post by brad,
@8BitCrab I appreciate the response. I wasn’t worried that they weren’t doing anything, I try to keep up with the game They’ve done more than I had ever expected coming into this Early Access title and I’m proud of the team and all they’ve done and how far they’ve come. I’m glad to say that I’ve been a long time supporter of this project and will continue to lend what ever support that my small stream can give it. My only concern is that I wasn’t seeing changes on those roadmaps, I was wondering if they had abandoned those ideas in lou of new ones and if so, where could I follow those long term ideas. I know they do Desktop Tuesday and push information out to the masses in that regard, I just wanted to know what was on the slab going forward.
@8BitCrab Looks like the new Alpha build is eating hella memory D: Things started to slow down on my stream today Going to restart the game and see how it goes!
How much time did you have the game open before noticing the memory leak, @DevolantTwitch?
If it always happen in a certain savefile, could you upload it so that we can investigate it?
Find the save folder for the saves you wish to upload. By default, they are located in C:\Program Files (x86)\Steam\steamapps\common\Stonehearth\saved_games (assuming a default Steam install).
Zip the folder.
Right click the folder (should be a long set of numbers).
Left click on Send to in the menu that appears.
Left click on `Compressed (Zipped) folder).
(Optional) Rename the folder to something different than the default set of numbers.
Upload the save.
If the zip is less than 10 MB, you can upload it directly. Either use the upload button or drag and drop it into the compose window,
If larger than 10 MB, upload it to a cloud storage site like Dropbox, Google Drive, File Dropper, etc. and post the sharing link here.
What is this? Artifacting or did they not completely dig out before building the road? I’ve had this happen before so I don’t think it’s linked to any engine upgrades.
Seems I’m experiencing a great bit of lag too that I hadn’t experienced before. Don’t know exactly what’s causing it. I’ll keep playing and trying different things, but I hadn’t even made it to the part I wanted to Which is playing with the water.
Thanks for the notes! I don’t know what’s up with the artifacting (could there be overlapping voxels in the road somehow?) but we do know that conversations introduced a lua lag that we will be fixing in A23.