Engine error with archer (ai spins: target out of range or sight)


When Kobold archer attack Crypt result in AI Spins : They can’t attack it :wink:

develop-2940 (x64)
@stonehearth/components/ai/ai_component.lua:566: (73778747 Sekv Blingg stonehearth:monster_tuning:kobolds:kobold_archer) has not yielded after 10 ai spins. Are they in a bad state? Last abort reason: Target out of ranged weapon range or not in sight
stack traceback:
radiant/modules/common.lua:237: in function 'report_traceback’
radiant/modules/common.lua:456: in function 'verify’
stonehearth/components/ai/ai_component.lua:566: in function <stonehearth/components/ai/ai_component.lua:524>
[C]: in function 'xpcall’
radiant/modules/common.lua:257: in function 'xpcall’
stonehearth/components/ai/ai_component.lua:524: in function '_thread_main’
stonehearth/services/server/threads/thread.lua:249: in function <stonehearth/services/server/threads/thread.lua:246>
[C]: in function 'xpcall’
radiant/modules/common.lua:257: in function 'xpcall’
stonehearth/services/server/threads/thread.lua:246: in function 'f’
radiant/lib/env.lua:15: in function <radiant/lib/env.lua:14>

Steps to reproduce:

  1. Crypt spawn near some Kobold archer (with luck of course)

Expected Results:
What Else ? ^-^

Actual Results:

No mods

savegame before : http://www.sendbox.fr/a1e0c135325a65cd/1461796692957.zip
savegame during this bug : http://www.sendbox.fr/fb816c931ba6afc5/1461800104783.zip

Version Number and Mods in use:
Alpha 16 - Build 2940

System Information:
Windows 10 Pro 64 bits
Dual-Core 2.3 Ghz (My old computer ^-^)
Nvidia GT 610
6Mo Ram
120 Go SSD

So, I take it the archer bug is still present in the patch that went out on the 27th?

The bug with heartling’s archer is resolved with alpha 16 - build 2940.Archer do not attack build structure with his bow.But the error occur for kobold’s archer.

Do I need to create a new world ? Bug still seems to be there, at least with old saves.

You have to wait bug fix if you can’t manage this.
If you want to continue save each time you do something important or use auto save feature but with unstable release it’s much better to save manualy.
Other last solution use the console (ctrl+c) select the kobold archer and tape destroy.

Good to see that its fixed for next update. So far this is the first error I have had playing the dev. version of 2490

Develop-2951 resolved a combat ai spin error as well as archers not being able to attack large objects. Let me know if you see any more of these errors. Thanks!