What Feature Types Apply to This Bug?

Other (Please Describe)

Other Type

Crashing again

What Type of Bug Is This?

Crash

Mod Loader

Fabric

Mod Loader Version

1.16.10

The Aether Version

1.20.1-1.5.2-beta.4-fabric

Is This Bug a Conflict With Another Mod?

Ultracraft 1.20.1-2.2.2

Client Log

https://gist.github.com/Aud999461/a6315b465da39c818dfa469ff1638e56

Crash Report (if applicable)

https://gist.github.com/Aud999461/8a0a6d041ad46e2014ee00a431582948

Steps to Reproduce

Steps to Reproduce
How to replicate!

1.Have the Aether and Ultracraft installed on an instance (even with Accessories Fabric 1.0.0 Beta 40 for 1.20.1 installed)
2. Try to open minecraft
3. Crashes immediately.

What You Expect To Happen

The game to boot up

What Actually Happened

It still crashes at startup

Additional Details

Hello me again w the same issue, I tried un-updating Accessories to the correct version stated in the dependencies and it didnt work still 😔
https://modrinth.com/mod/accessories/version/1.0.0-beta.40+1.20.1
https://modrinth.com/mod/aether/version/E4dcgfhG
https://modrinth.com/mod/absolute-ultracraft/version/6mAsNpBn
here are the links to the 'main' mods that seem to conflict, I tested them separately from the modpack I use incase that was causing any problems. And heres a screenshot of my bug testing modpack too incase it helps

Please Read and Confirm The Following

• I have confirmed this bug can be replicated without the use of Optifine.
• I have confirmed this bug is on the most recently supported version of Minecraft.
• I have confirmed the details provided in this report are concise as possible and does not contain vague information (ie. Versions are properly recorded, answers to questions are clear).
• I have confirmed this bug is unique and has not been reported already.
• If playing on a modpack, I have reported this bug to their issue tracker already.
• I have confirmed that I'm reporting a bug in The Aether I, not The Aether II.

oh sorry almost forgot to mention too, but I did try un-updating the fabric api too to "Fabric API 0.92.1+1.20.1" as stated in the dependencies, it still doesnt boot up.

@Aud999461 Seems like some class loading issues where I believe it could be here where the title screen may be class loaded really early with Cumulus to set up some code or something leading to this value being set up before mod loading is finished since class_442 is the TitleScreen. Not much to do on our side besides someone getting in contact with the UltraCraft Dev

d'aww so it has to be ultracraft to update w a fix?

Yeah I think this would have to be something UltraCraft would have to fix. Fortunately this issue should no longer occur in future MC versions since Cumulus' registration API was reworked, but in 1.20.1 this can't really be resolved on our end without doing a rewrite on that version too. For UltraCraft to fix this on their end I think all they would need to do is just change the config field to be initialized with init instead of when the class is loaded.