Crash logs for Minecraft Cursor + Sounds + Exposure: Polaroid: https://mclo.gs/hTbeLum
Crash logs for Sounds + Exposure: Polaroid: https://mclo.gs/rqFE7c3
The crash logs suggests a conflict between Minecraft Cursor and Sounds, but these two mods work fine together, by themselves. It's only when Exposure: Polaroid is added that the game crashes with these mods installed, upon launch with Minecraft Cursor + Sounds + Exposure: Polaroid, and upon opening the creative inventory if just using Sounds + Polaroid. Though strangely the game seems to be fine when just using Minecraft Cursor + Exposure: Polaroid.

I'm unsure if I should send these crash logs to any of the other developers atm, if you believe it's not the fault of your mod/if you need cooperation from the other mod authors I could post an issue on their respective githubs as well.

Edit: Additional context/clarification of mod combinations that cause the crash to occur.
Edit2: Added additional crash log to represent the two different crashes I'm talking about.

Hi, ExposurePolaroid is jar-in-jar'ing (or include on fabric) mixin extras for NeoForge -

You do not need to include mixin extras anymore as Fabric Loader now includes it natively.

This is what is causing the issues.

It does crash for me as well with the same error (if these mods are installed). But I don't see how Polaroid can cause this.
Polaroid (and Exposure) does not use/modify this specific class that's throwing an error. Maybe authors of Sounds can point something out.

It does crash for me as well with the same error (if these mods are installed). But I don't see how Polaroid can cause this. Polaroid (and Exposure) does not use/modify this specific class that's throwing an error. Maybe authors of Sounds can point something out.

Okay, thanks for the reply. I'll post this issue on the Sounds's github page in hopes they'll be able to figure out what's going on.

Here's the issue I posted to the Sounds's github page. Feel free to follow it to keep yourself updated on its progress. IMB11/Sounds#156

I also submitted it to the Minecraft Cursors github page, just in case/ whilst I was doing at it anyways. That issue can be found here: fishstiz/minecraft-cursor#14

Anyways, I'm off to bed, gn xd

@IMB11 Whoops. You're right, that fixes the issue. Thanks!
Fixed in 1.0.1.