[🐞]: Crash on world creation: mouseClicked event handler

[X66Herobrine66X]

BEFORE CONTINUING:

• Always check you are using the latest version of these mods and its dependencies
• Remove known problematic rendering mods such as Optifine, Sodium and others

Version-Loader

1.20.1-FORGE

Moonlight Lib Version

1.20-2.13-58

Describe the Issue

So, over the past few days I've experienced this crash multiple times in the process of developing my modpack. Upon opening the world creation menu, the game crashes. The description is always the same: mouseClicked event handler. It also seems to have something to do with VillagerTrades. I've included several crash reports from multiple iterations of my pack. Some of them list moonlight as a suspected mod, others don't.

Log Attachment

https://mclo.gs/sLaUkjC
https://mclo.gs/M5A4EEp
https://mclo.gs/TAHU37c

OPTIONAL: To Produce

1. Launch the game with requisite mods.
2. Go to singleplayer.
3. Click 'create new world'.
4. Game crashes.

OPTIONAL: Which mods are affected?

At one point the issue got fixed by removing supplementaries.

[X66Herobrine66X]

Update: removing Forgified Fabric API of all things seems to fix the issue. I'm not even sure why it was installed on my modpack, but removing it doesn't seem to break anything.

[Xelbayria]

Did the minecraft launched just fine? Forgified Fabric API, IIRC is a mod for FORGE to use with Sinytra Connector

[MehVahdJukaar]

Connector issues should be reported there, as their disclaimer says

[MehVahdJukaar]

also this is caused by old forge breaking stuff. use the version of the split. Still technically an issue of connector too as they should enforce a lower version

[X66Herobrine66X]

The what? What version of what split? 1.11.10 is the latest version of 1.20.1 Forge.

[X66Herobrine66X]

Connector issues should be reported there, as their disclaimer says

Yea but it says that in every crash log. How am I supposed to know its a Connector issue when it says Moonlight is a suspected mod.

[MehVahdJukaar]

I'm telling you now. Connector should put a warning at the top of the log that generally says to redirect all issues there. Obviously this would create so many false positives so it's very nice of them to have put it there. In this case however it is indeed it's issue.
Use NeoForge or 47.1.3 the split version

[MehVahdJukaar]

Report too

[Rearth]

This actually seems to be a conflict with forgified fabric api, which is used by a few mods recently on neoforge aswell (even without connector). I also ran into this issue on neoforge 1.21.