cabaletta
Baritone falls into lava in Open Nether
If you walk through open nether for long enough, the server will load new chunks which have lava flowing from the ceiling, which starts slowly flowing down. Baritone does not recognize this and walks into the flowing lava.
This one is quite tricky to be honest. I don't have a good solution in mind. Baritone does verify future costs, and if a future movement becomes impossible it will stop 5 steps beforehand. However there is no real fix for if lava falling from the ceiling happens to land right on top of it.
Every tick scan for unsupported lava or lava that's still expanding its flow, if there's any near the path just cancel immediately!
Some pseudocode to get you started ( Souper inefficient but whatever you know how to optimize it probably ) :
ArrayList<BlockPos> lavacoords=GetBlockCoords("Lava");
boolean blockspath=false;
for(BlockPos b : lavacoords)
{
for(int i=b.yCoord; i>0; i--)
{
BlockPos newblock=new BlockPos(b.xCoord,i,b.yCoord);
if(newblock.isSolid())
{
// I'm too lazy to write the checks for the lava flow, but basically simulate lava spreading if the block below is solid. Then check if it blocks the path. Example :
if(CheckIfBlocksPath(newblock.xCoord+2,newblock.yCoord,newblock.zCoord+1))
{
blockspath=true;
break;
}
}
else
{
// If it's air then continue down
}
}
}
thank you @EvilSourcerer i may incorporate something similar to that (just to annoy @0-x-2-2)
To be clear, if lava spreads into a future movement from the side or above, it will notice and cancel the path up to 5 movements ahead. This is only when lava spreads into its current movement from the side or above. https://youtu.be/6gIfONb6V7U
Was the update pushed out yet? Can you notify me when the appropriate commit is done?
I will let you know with a commit fixing this issue if/when that happens, however I have not thought of a good way to fix this. As I've said, it can only happen when lava falls directly on top of, or enters from the side, your current movement, not a future one, so no form of cost calculation can predict this. Therefore it just needs to be a heuristic that looks at where lava is spreading, or running it at faster tick speed to see where it will spread, or just looking for unsupported lava and ignoring sideways-spreading lava (which is not the best).
It's really hot... I fall in this bug and find this 7 years ago issue. Hope the bug could be fixed as soon.
