[1.21.1 | 2.0.0-beta.5/2.0.0-beta.6 | Axiom] Game Fails to Launch: No Crash Log or Errors Generated

[Diaxium]

Mod Name

Axiom

Mod Homepage

https://modrinth.com/mod/axiom

Minecraft version

1.21.1

Describe the bug

The game fails to launch and leaves no errors to go off of.

Steps to reproduce

1. Ensure you are running the latest version of Neoforge for Minecraft 1.21.1 (optional: GraalVM 22.0.2; issue persists across different JDK/JRE versions).
2. Install the following mods:
   • Forgified Fabric API
   • Connector Extras
   • Sinytra Connector (v2.0.0-beta.5+1.21.1 or newer)
   • Axiom (Fabric: Axiom 4.3.3 1.21.1)
3. Launch Minecraft (I was running in a fresh setting with no logs, no config files, etc)

Logs

v2.0.0-beta.5+1.21.1: Latest.log: https://mclo.gs/vmYfg4f, Debug.log: https://mclo.gs/2FrTooS
2.0.0-beta.6+1.21.1: Latest.log: https://mclo.gs/e6mN4r9, Debug.log: https://mclo.gs/kEIE2ZW

Additional context

I find it hard to believe that I’m the only one experiencing this issue, especially since it’s been about 23 days since the connector was updated to v2.0.0-beta.5+1.21.1 and 2.0.0-beta.6+1.21.1. However, no one else has reported a similar problem. My previous setup with 2.0.0-beta.4+1.21.1 worked perfectly, but with the updated version, my instance fails to launch without generating any crash logs or errors. I’ve followed the instructions precisely, only using the three required mods, and I’ve checked both the Discord and issue tracker but found no reports matching my situation.

The only remotely related issue I came across was one involving Embeddium. I even tested adding Embeddium to my setup as described in that post, following the steps around the issue, but the outcome was the same—a failed launch with no additional information provided in the logs.

[PainttbuI]

Hello, what setup did you use previously that worked?

[Moulberry]

This is caused by the same issue as #1634. It seems like jar-in-jar libraries are being loaded in a way where they can't access anything