New checkpoint added to Sarkoth routine?

[Ravos]

Fixed

Have been running 3 bots very smoothly and got another bot to 60 today.
Am using identical settings as the other 3 that are still going strong right now... but there is a weird thing happening.

Like normally I get the checkpoint at the gate area which is 100 yards in front of Sarkoths hut. The end of the Sarkoth routine is teleporting to town and logging out to repeat the profile again.
But now as soon as I teleport to town and either move manually 10 yards to the right or if it goes for selling/salvaging automatically from time to time it triggers a new checkpoint in town??
This makes my bot logging into town and doing nothing.

Anyone experiencing the same or has tips to fix it?

 

[boss007]

no just another pointless post about sarkoth lol.

chec kyour config.

 

[shinavaka]

Reset your checkpoint, go to different quest, then remake game set back to northwest gate and get cp again, Usually fixes it

 

[Ravos]

I wouldn't have posted a topic if I didn't try to fix it for about 2 hours.
Changed the checkpoints multiple times but effect is the same.

And boss007 you can better first post in a useful way

 

[The-Lord]

Set Inactivity time to 0 and check

 

[Ravos]

Set Inactivity time to 0 and check

Has been zero since start but thanks for the suggestion.


If I look inside the logs I get this 3 rows each time I join:

[20:45:03.255 N] Game joined, Reloading profile.
[20:45:03.633 N] Failed to load profile: Cannot change the current bot, while the bot is running!
[20:45:28.371 N] Stopping the bot.

Still works but fails when moving in town, maybe this cause the extra checkpoint will try to find out how to fix it since it uses identical input as my other bots.

 

[tesslerc]

Happens when you select wrong quest.. Make sure its ENTER THE CELLAR and not q2.1 but q2.2

 

[Ravos]

Happens when you select wrong quest.. Make sure its ENTER THE CELLAR and not q2.1 but q2.2

Just found it out too ^^ Thanks for confirming.
With my past bot accounts I went a bit further by coincidence so that I didn't recognize it as a solution.

Topic can be closed is fixed.