Skip to content
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

Game crashes when loading world with CensoredASM #3914

Closed
4 tasks done
JaneStateDog opened this issue Apr 16, 2023 · 7 comments
Closed
4 tasks done

Game crashes when loading world with CensoredASM #3914

JaneStateDog opened this issue Apr 16, 2023 · 7 comments
Labels
bug Something isn't working

Comments

@JaneStateDog
Copy link

Some information

Operating system: Windows 10
Java version: 17
Minecraft version: 1.12.2
Forge version: 14.23.5.2860
Baritone version: baritone-api-forge-1.2.17
Other mods (if used): CensoredASM-5.6, mixinbooter-7.1

Exception, error or logs

https://mclo.gs/UOg2JG3

How to reproduce

With CensoredASM, MixinBooter, and Baritone the game crashes if I boot into a world. With just MixinBooter and Baritone the game has no issues.

Modified settings

Nothing has been 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.
@JaneStateDog JaneStateDog added the bug Something isn't working label Apr 16, 2023
@wagyourtail
Copy link
Collaborator

Most likely caused by #3859 (comment)

@ZacSharp
Copy link
Collaborator

That one messes fields up, not entire classes like the crash report suggests.
I'd like to see the full log though since the actual error might have happened earlier. Classloaders like to respond with "not found" if an earlier attempt at loading the class failed without a crash.

@JaneStateDog
Copy link
Author

Here ya go!

latest.log

@ZacSharp
Copy link
Collaborator

Are you sure the crash report and the log file are from the same crash?
The log file contains the expected IllegalAccessError, but also says the game crashed as a direct consequence of the IllegalAccessError and not later by a NoClassDefFoundError (which is what your crash report shows).

@JaneStateDog
Copy link
Author

Oh, no sorry, they are not. I booted up the game and did the bug again to produce the full log. So sorry, not sure what was going through my head there, haha. Here is a new log and crash report, both from the same crash. I hope this helps.

Crash:
https://mclo.gs/OCRJ3kS
crash-2023-04-16_18.05.07-client.txt

Log:
latest.log

@ZacSharp
Copy link
Collaborator

ZacSharp commented Apr 16, 2023

Does disabling the optimizeFMLRemapper setting of LoliASM help?
If so this is #3820

@JaneStateDog
Copy link
Author

Oop, yeah that 100% fixed it. Awesome! Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants