Persistence through disconnect
I think we can just filter out TickEvents with Type.OUT in PathingControlManager actually? Or does it have to be higher up, in PathingBehavior? I really don't know which is better. I tried both a while back and they both caused really strange issues on rejoin.
and i know for a fuckin fact that some people will demand that baritone resume on rejoin but nOT while in 2b queue ONLY when spawned back in, so it has to be even more complicated and detect that in order to be useful at all
Maybe disconnect can do #pause, then when back on 2b we can manually type #resume?
@ThebesAndSound but surely if we have to type #resume then it's not persistence, you might as well just do #goto again
@Haxified #goto isnt the only baritone command that #pause or persistence is useful to, sometimes you can't continue the job by simply repeating the original command. Default should be #pause on dc if persistence isn't possible or realistic.
This would be incredibly useful if you're using #mine or #goto with autodisconnect and reconnect, or just in general if you get kicked while you're AFK.