We’ve identified a few bug fixes and enhancements that we don’t want to wait to get in your hands (since the first unstable release of Alpha 17 is soon… but not that soon). So probably the last update to Alpha 16. But never say never again, and all that.
For the moment, this release is only on our Steam latest (unstable) branch. We will move it to the stable branch after a short evaluation period.
Fixed crash when trying to load a game again after having already loaded a game
Fixed bug that prevented scaffolding from being built for slabs after game load
Fixed two bugs that caused combat units to ignore enemies
Fixed melee units not moving to defend a location while in combat
When defending a location, units will leave their post to go eat and sleep. You might want to put food and beds near their defense point.
Fixed bugs that were slowing down pathfinding
Fixed a few placement direction indicators that were off center
Fixed two bugs that caused mining zones not to be mined
Fixed General’s Gong recipe taking the wrong ingredient
Ranged units will now kite their enemies
Improved target selection code. Hearthlings will now focus fire at enemies that are low on health.
Changed sound effects for cleric healing
Trapping grounds can now be placed on mountains. The spawn rate on mountains is lower though.
Mining zones now have a max size of 40. You can still merge them to create larger zones though, but this is not recommended for performance.
I joyfully went to try new version! However…
I tried stable version it was still r553. I thought r559 is not ready for steam normal branch yet at this time.
So I tried latest branch, but stonehearth won’t start up. Steam client asked me force to close?/wait?. After restarting steam client, it’s saying stonehearth is still running. Even after rebooting my windows.
I had to remove app.manifest file remaining in the steam library folder. And I had to reinstall stonehearth as normal branch…(I repeated these progress few times)
As a result, just failed to try new version…
Hi @linda, for me, It’s still r553 for normal branch.
So I tried latest branch a minute ago again, it still makes steam client broken.
When I try to remove stonehearth.exe process from task manager it says “access denied”.
Because of this, I had to reboot windows and remove app manifest file of stonehearth.
Existing manifest file makes steam client unable to run any other games, arguing stonehearth is still running.
Once manifest file removed, the game is indicated as not installed, so I can install it again.
Now I just installed normal branch r553, and I am waiting for problem to be solved.
The notification on the dev blog has been updated to reflect that release-559 is currently only on our Steam latest branch. We’ll move it to the stable branch after an evaluation period (probably tomorrow, no guarantees though!).
This build contains fixes and features we didn’t want to wait to release – but at the same time, we’re cautious about pushing things that have been tested only internally straight to the stable branch. So if you’re on the unstable branch, please give it a whirl and let us know if it’s working as intended!
Since the update the sheep wool has been having an issue… It started with this error.
c++ exception: invalid file path ‘/stonehearth/data/effects/fursplosion_effect/growing_wool_effect.json’.
[C]: in function 'load_json’
radiant/modules/resources.lua:33: in function 'load_json’
radiant/modules/effects/effect_tracks.lua:34: in function '__init’
radiant/modules/common.lua:20: in function 'EffectTracks’
radiant/modules/effects/effect_manager.lua:84: in function '_add_effect’
radiant/modules/effects/effect_manager.lua:69: in function 'start_effect’
radiant/modules/effects.lua:21: in function ‘run_effect’
…_resource_node/renewable_resource_node_component.lua:161: in function ‘renew’
…_resource_node/renewable_resource_node_component.lua:34: in function '_fn’
radiant/controllers/timer_controller.lua:95: in function 'fire’
radiant/controllers/time_tracker_controller.lua:82: in function <radiant/controllers/time_tracker_controller.lua:82>
radiant/controllers/time_tracker_controller.lua:82: in function ‘set_now’
…hearth/services/server/calendar/calendar_service.lua:379: in function ‘_on_event_loop’
…hearth/services/server/calendar/calendar_service.lua:37: in function 'instance’
radiant/modules/events.lua:206: in function <radiant/modules/events.lua:200>
[C]: in function 'xpcall’
radiant/modules/common.lua:257: in function 'xpcall’
radiant/modules/events.lua:200: in function 'trigger’
radiant/modules/events.lua:269: in function '_trigger_gameloop’
radiant/modules/events.lua:320: in function '_update’
radiant/server.lua:62: in function <radiant/server.lua:58>
quote A term in video gaming and elsewhere to describe when a ranged fighter skirmishes with a hand-to-hand fighter by running and shooting. This can have 2 purposes: a) to damage the enemy while staying outside of hand-to-hand range, or b) to make the enemy follow you so you can lead them to a specific location
I tried r559 at latest branch a minute ago!
My building stucked is started to be built! Yes!! I love it!
Another thing I want to say is, I thought most of all efforts done in combat update is messed up.
I had to become angry because my army keep ignores battle command… hit that guy, hit that guy, no no not that guy, no don’t go to pick up loots! hey where are you going? no no no no stop don’t go don’t go don’t chase DO NOT CHASE! hit this guy first! such things… Armed hearthling sometimes go to pick up loots when I command to attack… even just near the enemy…
And another critical bug I found is a footman was an archer keep making a distance(probably archer’s range) against enemy and just looking enemy and mimicking archer’s kiting motion while holding a sword. Lots of such AI bug is temporarily fixed when I save&reload game, but it messed up a few minute later again. While AI is messed up, if I command defend position, it ignores further any other commands until save/reload…
Although I’m happy with most of 559 there is one thing that worries me. Soldiers will leave their post to sleep and eat while on defend duty.
Up till now Whenever I was doing anything outside the security of the city walls I was using a party rota of 8 hours on defence mode. It worked perfectly and the civilians were protected 24hrs a day.
Now I’m risking my city and workers to be left undefended should the soldiers decide to go to sleep all of them at the same time.
I don’t know whether I’m happy with this change.
I can’t speak for “most of the people”, only for me. And I prefer my hearthlings to be reliable. With this change they are not.
After writting the first post I realized another thing. I also used the defend command to gather the troops before an attack. With It you could lauch the parties together and not one by one as they arrived.
The defend command was the only one that allowed it. With the other commands as soon as they hit the banner the soldiers go back to patrolling. Now, it will not work anymore. We are in the hands of the hearthlings whims.