Find_healable_target_observer.lua:296 Engine Error

Summary:
Hostile mob (wolf, in this case) runs within range of town, triggers guards, who give chase. Mob is too fast for the guards, and doesn’t care that they’re chasing. Just as the wolf is about to despawn, goblins run in from a different raiding party to intercept the guards. Once within combat range, this engine error is triggered:

release-753 (x64): ...earth/ai/observers/find_healable_target_observer.lua:296: attempt to index local 'ic' (a nil value)

release-753 (x64)
…earth/ai/observers/find_healable_target_observer.lua:296: attempt to index local ‘ic’ (a nil value)
stack traceback:
radiant/modules/common.lua:245: in function ‘report_traceback’
radiant/modules/common.lua:256: in function <radiant/modules/common.lua:250>
…earth/ai/observers/find_healable_target_observer.lua:296: in function ‘_get_target_score’
…earth/ai/observers/find_healable_target_observer.lua:280: in function ‘_update_heal_score’
…earth/ai/observers/find_healable_target_observer.lua:265: in function ‘fn’
radiant/modules/events.lua:288: in function <radiant/modules/events.lua:285>
[C]: in function ‘xpcall’
radiant/modules/common.lua:265: in function ‘xpcall’
radiant/modules/events.lua:285: in function ‘trigger’
radiant/modules/events.lua:370: in function ‘_fire_async_triggers’
radiant/modules/events.lua:445: in function ‘_update’
radiant/server.lua:61: in function <radiant/server.lua:58>

Expected Results:
Normal, error-free combat.

Actual Results:
Engine Error.

Attachments:
megashub-A22-R753-combat-engine-error.zip (8.8 MB)
stonehearth.log (3.0 MB)

Version Number and Mods in use:
A22.5 R753 x64, vanilla

2 Likes

Thanks for reporting this, @megashub (and for the savefile) :slightly_smiling_face:

1 Like

Summary:
In my current game the attack Goblin Parties with Healers are not getting healed by their Healers

Attachments:
here is a save were a goblin party with healers attacks my village

Version Number and Mods in use:
r753 x64
homf mod
slabs with terrain colours mod

2 Likes

This should be fixed for next build.

2 Likes