#elytra bug, when going to certain cords
AlsoShy opened this issue ยท 1 comments
Some information
Operating system: Win 11
Java version: jdk 8, java 8
Minecraft version: 1.12.2
Baritone version: Beta
Other mods (if used): Rusherhack, future, mio (1.12.2), Cowdupe, optifine
Exception, error or logs
It doesnt crash the game
so no need
How to reproduce
- go like a 100 blocks out
- then do #goal 0 ~ 0
- afterwards do #elytra
- then wait until the end when it starts spiraling
- and then there should be a decent lag spike for 3 sec exactly.
Modified settings
nothing modified
Final checklist
- I know how to properly use check boxes
- I have included the version of Minecraft I'm running, baritone's version and forge mods (if used).
- I have included logs, exceptions and / or steps to reproduce the issue.
- I have not used any OwO's or UwU's in this issue.
A bit of lag is kinda to be expected if you are in a huge open area far away from a landing position since it uses floodfill to find a landing spot.
However there have been recent changes to landing logic and there is a (small) chance that those affect your problem so can you please make sure you are using the latest CI build? (the download button is "Artifacts" and only works while logged in to github)