Pathfinding Through Water

[Yzrsah]

Describe your suggestion

I'm trying to use Baritone to escape spawn on Anarchy server.
Functionality is working well, parkour, drop down, block placement, all are working.
The no.1 thing that is stopping me, is the water.
When it gets into the water, Baritone stops and pathing is cancelled. (Possibly leaving you drowning)
Baritone only continues pathing if you are on top of the surface of the water.
After the pathing is cancelled, I need to swim through water and get to the surface, then enable Baritone again.
Can be stopped repeatedly by this. Also it stops on surface of water, due to lack of perfect flatness. And if you sink under the water for even a split second, Baritone pathing gets entirely cancelled and you start sinking to bottom / drowning.

Settings

A setting to allow pathing to continue underwater.
Possibly also a setting to allow a maximum distance to path underwater.

Context

It could help to make Baritone more persistent.

Final checklist

• I know how to properly use check boxes
• I have not used any OwO's or UwU's in this issue.

[ZacSharp]

Can you show how it gets into water and cancels? That shouldn't happen during normal path execution.

Staying at the surface when ending path execution on water has already been suggested long ago, but wasn't implemented yet (someone do it please).

Baritone should already have some limited ability to get out of water, though that's mainly ascending straight upwards and I'm not sure how that interacts with flowing water. Swimming on the surface of flowing water is technically possible, however it takes quite some effort to implement and I'm not convinced it would be all that useful, since normally the better path will always be to either scaffold over the water or build a tunnel around it. Some hacky "best effort" sideways movement out of flowing water should be possible with less effort (and performance impact).

Lastly, managing the amount of oxygen left is theoretically possible, but probably practically infeasible. In short, for A* to work well, all movements have to be independent of how their starting position was reached. All information movements depend on must be part of the state ("position") the pathfinder uses, so including oxygen left would require pathfinding in x,y,z,oxygen coordinates, turning every position into a dozen individual states.
(There might be some trickery with oxygen being mostly monotonic and in sync with path length, but I wouldn't bet on that)