[Bug] Crash On Start With Sodium In 1.21.1

by ADMIN 43 views

Bug Report: Crash on Start with Sodium in 1.21.1

Describe the Bug When attempting to use the Copycat+ block in Minecraft 1.21.1, the game crashes with a java.lang.NoClassDefFoundError exception, specifically referencing Sodium compatibility classes. This issue is reproducible with a custom build against the #08051395b0dfeeb442ba2bffeb24a2a4fb95ab6d branch head.

To Reproduce The following steps can be taken to reproduce the crash:

Mod List

The following mods are installed:

  • neoforge-21.1.162 (modloader): neoforge
  • copycats-2.2.2+mc.1.21.1-neoforge.jar: copycats
  • crash_assistant-neoforge-1.21.1-1.7.12.jar: crash_assistant
  • create-1.21.1-6.0.4.jar: create
  • jei-1.21.1-neoforge-19.21.0.247.jar: jei
  • sodium-neoforge-0.6.13+mc1.21.1.jar: sodium

Steps to Reproduce

  1. Install the above-mentioned mods.
  2. Launch the game.
  3. Create a new creative peaceful superflat world.
  4. Enter the world.
  5. Add the Copycat Byte from the creative menu.
  6. The game will crash.

Expected Behavior The expected behavior is to be able to take the Copycat block from the Creative menu, place it, and apply a texture without any issues.

Desktop Information The following information is relevant to the issue:

  • Minecraft Version: 1.21.1
  • NeoForge Version: 21.1.162
  • Create Version: 6.0.4
  • Sodium Version: 0.6.13 (for NeoForge)

Crash Logs The crash logs have been uploaded to gnomebot.dev:

Mod List Changes The mod list has not been modified beyond the latest successful launch.

Additional Context The issue was encountered with a custom build against the #08051395b0dfeeb442ba2bffeb24a2a4fb95ab6d branch head, which includes EMI support checkin. Disabling Sodium resolved the crash. It is possible that the issue is related to developing against a different version of Sodium.

Possible Solution Based on the provided information, it is possible that the issue is related to Sodium compatibility classes. The solution may involve updating Sodium to a compatible version or modifying the mod to work with the current version of Sodium. Further investigation is required to determine the root cause of the issue and provide a suitable solution.
Q&A: Crash on Start with Sodium in 1.21.1

Q: What is the issue with Sodium in 1.21.1? A: The issue is that the game crashes with a java.lang.NoClassDefFoundError exception when attempting to use the Copycat+ block in Minecraft 1.21.1, specifically referencing Sodium compatibility classes.

Q: What mods are installed to reproduce the issue? A: The following mods are installed:

  • neoforge-21.1.162 (modloader): neoforge
  • copycats-2.2.2+mc.1.21.1-neoforge.jar: copycats
  • crash_assistant-neoforge-1.21.1-1.7.12.jar: crash_assistant
  • create-1.21.1-6.0.4.jar: create
  • jei-1.21.1-neoforge-19.21.0.247.jar: jei
  • sodium-neoforge-0.6.13+mc1.21.1.jar: sodium

Q: What are the steps to reproduce the issue? A: The steps to reproduce the issue are:

  1. Install the above-mentioned mods.
  2. Launch the game.
  3. Create a new creative peaceful superflat world.
  4. Enter the world.
  5. Add the Copycat Byte from the creative menu.
  6. The game will crash.

Q: What is the expected behavior? A: The expected behavior is to be able to take the Copycat block from the Creative menu, place it, and apply a texture without any issues.

Q: What is the desktop information relevant to the issue? A: The following information is relevant to the issue:

  • Minecraft Version: 1.21.1
  • NeoForge Version: 21.1.162
  • Create Version: 6.0.4
  • Sodium Version: 0.6.13 (for NeoForge)

Q: Where can I find the crash logs? A: The crash logs have been uploaded to gnomebot.dev:

Q: What is the possible solution to the issue? A: Based on the provided information, it is possible that the issue is related to Sodium compatibility classes. The solution may involve updating Sodium to a compatible version or modifying the mod to work with the version of Sodium. Further investigation is required to determine the root cause of the issue and provide a suitable solution.

Q: Is there any additional context that may be relevant to the issue? A: Yes, the issue was encountered with a custom build against the #08051395b0dfeeb442ba2bffeb24a2a4fb95ab6d branch head, which includes EMI support checkin. Disabling Sodium resolved the crash. It is possible that the issue is related to developing against a different version of Sodium.