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.
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 âŚ
Thank you for confirming
At the moment, I donât know when I can add such a feature.
hi all
fastest way to solve the problem is to replace
After that you can use the script even if you dock. it goes in waiting position.
quick and dirty
Hope it helps.
Thank you for sharing, yes this implements a change to not finish the session
But unfortunately, it isnât what I originally asked for. I want to pause the session when the route ends so I can do other things (for example, run a combat mission) then set a new path and initiate again. With this change in place the bot still has control of the session so you canât do anything.
I did spend a fair bit of time looking at the code back when I first raised this and saw that line 154 was where the change needed to be but I couldnât find a way to initiate âpause modeâ in any of the code on github. Not just for this bot, I looked through them all.
Maybe my lack of familiarity with elm or maybe I just didnât look hard enough but if a pointer could be given as to how to initiate pause then that would be great.
Yes, thats right, I was thinking that workaround would at least help some people get closer to a solution, but its not as good as the switch to the pause mode.
The current API does not have such a functionality, and I am not sure if adding it to the bot API has any advantage over adding it into the session configuration.
I still need to expand the session configuration to support the âpause instead of stopâ functionality.
Ok. Thanks for getting back to me, I didnât want to seem like I was jogging your elbow.
I am also glad to see that I wasnât being silly, there currently isnât a way for the code to initiate the pause.
I suspect this change will be âgood enoughâ if I also disable the scanning across modules to activate them.