cabaletta
CustomGoalProcess issue (maybe)
I'm encountering a crash in Baritone when running a custom script with JsMacros (v1.9.2) on Minecraft 1.18.2 (Fabric). The crash occurs after entering a dungeon, specifically when Baritone's CustomGoalProcess tries to execute pathfinding/goal-related operations. The script's logic involves detecting when the player moves from coordinate A (the dungeon entrance) to coordinate B (the dungeon spawn); after confirming the player is near coordinate B, it implements a 10-second delay intended to ensure proper chunk loading before running a sub-script that initiates Baritone's goals, such as pathfinding and monster targetin
Version 1.18.2 is over 600 commits behind the currently maintained version 1.19.4. Switch to that and see if it still crashes. If the server you're using doesn't support 1.19.4, use ViaVersion. If the mods you're using don't support 1.19.4, you got to remove something. You're not getting help for legacy versions.
Version 1.18.2 is over 600 commits behind the currently maintained version 1.19.4. Switch to that and see if it still crashes. If the server you're using doesn't support 1.19.4, use ViaVersion. If the mods you're using don't support 1.19.4, you got to remove something. You're not getting help for legacy versions.
Actually, I used to use the 1.20.1 Fabric client with the Meteor mod, and when I joined the same server, I encountered exactly the same error. The only reason I switched to 1.18.2 is that the server core I'm playing on uses 1.18.2. Also, the reason I didn't show the error log from my 1.20.1 version is that it was in Chinese, which would make debugging inconvenient. However, I'll still try switching to version 1.19.4 and install ViaFabricPlus to see if the same error occurs.
1.20.1 Same Crash 2025-08-07-4.log
Sigh, there is exactly one new IllegalStateException() in Baritone (in BackfillProcess.onTick), which is not reachable from the callstack given here (i.e. from CustomGoalProcess.onTick).
Can you please try using an unoptimized baritone build to get a better stack trace and tell us the precise version you used? I'd like to know which line of code the exception comes from.
