How hard would this be? It would be very useful for mission running as you could just let the bot do all the navigating. Personally, I am fine with this burning online session time.
I mean I could maybe have a go myself as the logic would seem simple ie where it decides to end now just put in a branch to pause based on the toggle. But I think I would struggle to add the toggle to the initiation screen etc.
What does “pause” mean to you? Do you mean the bot should continue running when there is no route anymore left in the info panel?
Do you mean it should continue sending inputs as soon as there is a new route in the info panel?
That would be very easy to implement.
The bot already has a pause function if you hit ctrl alt shift, input pauses but the bot keeps running. Basically the toggle should cause the bot to use that as an override instead of finishing.
1 Like
Thank you for the clarification.
That is an interesting idea. I will check how this could be added without breaking something else.
One way would be adding a toggle like this in the session setup:
What do you think about such a solution?
In the case of the travel bot, the branch leading to finish is this:
So the bot only tries to finish the session as long as the route info panel is empty.
Actually, it might be better to place such a checkbox somewhere reachable from the view of the running session, allowing to enable/disable this at any time 
It looks exactly like what I was asking for but I knew it would be more complex than I originally thought …
1 Like
Thank you for confirming 
At the moment, I don’t know when I can add such a feature.