Unexpected error (feedback, fix pls, thx)

[Qra]

Hi,

Just daily amount of feedback.

Bot does hes job really well, buuut just now:
bot went Dried Lake like usually, and found exception:

2015-12-21 12:44:26,257 [50] DEBUG CustomLogger (null) - [ExilePather] Now reloading the pathfinder.
2015-12-21 12:44:26,645 [50] DEBUG CustomLogger (null) - [ExilePather] Now creating the navmesh.
2015-12-21 12:44:32,545 [50] DEBUG CustomLogger (null) - [ExilePather] The navmesh has been created.
2015-12-21 12:44:32,546 [50] DEBUG CustomLogger (null) - [ExilePather] The pathfinder has been reloaded.
2015-12-21 12:44:32,751 [50] ERROR CustomLogger (null) - [Tick] Exception during execution:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at Loki.Bot.GridExplorer.Tick()
at Loki.Bot.Logic.Bots.OldGrindBot.AreaStateCache.????????????????????????????????????????()
at Loki.Bot.Logic.Bots.OldGrindBot.AreaStateCache.Tick()
at Loki.Bot.Logic.Bots.OldGrindBot.OldGrindBot.Tick()
at Loki.Bot.BotManager.?????????????????????????????????????????(IBot )
2015-12-21 12:44:33,779 [50] ERROR CustomLogger (null) - [Tick] Exception during execution:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at Loki.Bot.GridExplorer.Tick()
at Loki.Bot.Logic.Bots.OldGrindBot.AreaStateCache.????????????????????????????????????????()
at Loki.Bot.Logic.Bots.OldGrindBot.AreaStateCache.Tick()
at Loki.Bot.Logic.Bots.OldGrindBot.OldGrindBot.Tick()
at Loki.Bot.BotManager.?????????????????????????????????????????(IBot )
(...)

It looks like that, and bot continious to error, when i click "start" again,
http://imgur.com/0vVMIch

Full log attached

Why is that, can we avoid it in future?

Best Regards
Qra

 

[pushedx]

Try restarting the bot and making a new instance. Nothing has changed recently with that code, so it might be a rare case of an instance whose pathfinding data the bot can't handle.

 

[Qra]

Try restarting the bot and making a new instance. Nothing has changed recently with that code, so it might be a rare case of an instance whose pathfinding data the bot can't handle.

I mean that happend only once so far, so yeah.

Best Regards

 

[pushedx]

I think I saw it once as well after the new update, but I'm not sure what it was from. Since terrain generation changes so often in this game, and there's no way to test or see even a fraction of the generated levels, random things like this are a possibility.