Baritone AI pathfinder

Baritone AI pathfinder

72.7k Downloads

Crash in forge 1.16.5

AlexChecker opened this issue ยท 7 comments

commented

Some information

Operating system: Windows 11
Java version:
java version "1.8.0_301"
Java(TM) SE Runtime Environment (build 1.8.0_301-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.301-b09, mixed mode)
Minecraft version:1.16.5
Baritone version: baritone-standalone-forge-1.6.3
Other mods (if used): create,flywheel,mantle,tinkersconstruct

Exception, error or logs

latest.log
(Also it throws nullpointer exception as error when world closes)

How to reproduce

load with other mods and try to walk somewhere

Modified settings

nothing was 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.
commented

Can you reproduce this without any other mods installed?

commented

I can second this. Joining worlds is fine, but as soon as you try to move it crashes. Take out baritone and everything is fine. I think it has something to do with some of the latest forge versions. Earlier versions of the modpack I'm playing were working fine.

commented

Someone had this issue in the discord so I was able to find that this is caused by Flywheel when you cross a chunk border

commented

I can validate that Flywheel is the issue on 1.16.5 in Create: Above and Beyond v1.1 modpack.

commented

A temporary workaround for this if Flywheel is installed, use the command /flywheel chunkCaching off before you start moving and you should be able to walk around and use Baritone.

I'm unsure what the issue is, but once you pass a chunk border with Flywheel caching on it will crash/disconnect you. I feel like this issue should be renamed to reflect it's an issue with Flywheel instead of generic crash.

commented

Try it on 1.15.2

commented

@ejsupernova why? There is already a workaround that does not require switching version.