-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unsupported CPU message on neoforge, works on fabric #4656
Comments
Can confirm this happens with a fresh install of the Neoforge and Baritone versions you listed (as well as Neoforge 21.4.95). The PC I used runs Ubuntu on a x86 CPU and I also used it a week ago to record the video here. As in your case both log files show no indication of the error besides the chat message. However the prismlauncher log window does show an exception, along with output from nether-pathfinder. log excerpt
Additionally the JVM segfaulted when I closed the game, no idea whether that's related. |
Using the unoptimized build from the same CI run works though and the segfault also disappears. (api build doesn't work) Unoptimized being the only variant that works hints at proguard/optimization being the problem, though stripping |
Proguard stripping the constructor was indeed the problem. That specific constructor is only accessed via JNI so proguard thinks it is unused. |
Some information
Operating system: openSUSE Tumbleweed 20250217
Java version: 21.0.3
Minecraft version: 1.21.4
Baritone version: baritone-standalone-neoforge-1.11.1-2-ga0f100f4 from https://github.com/cabaletta/baritone/actions/runs/12592616905
Other mods (if used): -
Launcher: Prism Launcher 9.2 (flatpak)
The exact same configuration works when using the fabric standalone variant (baritone-standalone-fabric-1.11.1-2-ga0f100f4 from same artifact)
Exception, error or logs
latest.log
debug.log
How to reproduce
#thisway 1000
#path
#elytra
Modified settings
from
baritone/settings.txt
Final checklist
Let me know if there's more helpful info to provide
The text was updated successfully, but these errors were encountered: