Goblin in sight - Inactivity timer tripped!

[vid-jey]

I do not know where I'm writing.
There is a problem when it detects a goblin, when it is out of reach. Treasure Goblins: Kamikadze.
This is especially true in the towers.
Inactivity timer is triggered, a new game after that is created.
It would be good to do so, so that you can limit the distance of detection goblin.
(There may be other ways to solve this problem).

[15:54:39.485 N] [GilesTrinity] Goblin #1 in sight. Distance=116,7208
[16:26:40.459 N] Inactivity timer tripped! Leaving game
[16:26:40.459 N] Leaving game
[16:26:40.481 D] Navigator.Clear
[16:26:40.484 N] Last run acquired 15860 gold.
[16:26:40.484 N] [UnstuckMe!] Resetting5149296
[16:53:27.633 D] Start/Stop Button Clicked!
[16:53:27.635 N] Stopping the bot.

 

[vid-jey]

Only that it happened again.

[23:45:19.862 N] [GilesTrinity] Goblin #15 in sight. Distance=115,1513
[23:47:21.155 N] Inactivity timer tripped! Leaving game
[23:47:21.156 N] Leaving game

 

[Diabloguy69]

yes has been happening to me as well. I don't know if a beta patch did it or what but I dont remember having this problem 1-2wks ago...

 

[vid-jey]

Yes, I also think that before this problem was not

 

[herbfunk]

Just happened to me also.

 

[zippysticks]

The problem is db is getting updates while trinity stays the same so of course problems will occur if one of them is outdated.

 

[Moley]

Turn down goblin priority, problem fixed

 

[vid-jey]

I already did, helped or not, I do not know

 

[vid-jey]

still relevant
I would like the bot was not trying to attack a goblin on a very large distances.

 

[vid-jey]

I hope that Giles recovers and sees this topic
up