ZacSharp

Sorry, I haven't worked on this since a year ago. It is fully functional and if you know how to compile Baritone you can use it. I just don't like...

Did you find the reason for the crash?

What would such a fix look like? * Not extending `BlockPos`. A very disruptive change for anyone using `BetterBlockPos` and making it far less convenient to use. * Making `BetterBlockPos`...

Can you maybe provide the place leaking the `BetterBlockPos`? Reproducing on your branch failed and I currently don't have the time to figure it out using just the error message.

Also got this symptom with a 1.12.2 Forge development and was able to verify it in a production environment. Yaw is copied from the input, velocity and position stay unchanged....

 Is there any specific reason for this? To me it looks like it is the reason why `applyInput` doesn't work on 1.12 and 1.8 (comment exists on both branches,...

Don't take this as a promise for anything. The server for which I need Litematica is on 1.17.1 so there will be a drop in motivation once this is working....

Sorry, I didn't see them linked anywhere here on this repo so I assumed the situation was still the same. Can you maybe give links to them so I can...

> I haven't tested them at all to see how well they work, but I wouldn't expect any major issues if they are basically the Fabric code slapped on top...

Baritone can't properly handle carpets on non-full blocks (e.g. double carpets). The easy fix would be checking `pos.up` in `canWalkOn` but that would almost double the amount of block queries...