Firmament 3.11.0 and 42.0.0 crashes on client initialization on Minecraft 1.21.8 (3.9.0 works)

[ItsCl4Y]

Firmament Version

Firmanent 42.0.0/3.11.0

Bug Description

Firmament 3.11.0 consistently crashes during client initialization on my setup.
Downgrading Firmament to 3.9.0 fixes the issue immediately, with no other changes.

This started happening today: the same setup worked earlier (around 12:00), then began crashing later without changing Firmament itself.

Environment:

• Minecraft: 1.21.8
• Mod Loader: Fabric
• Fabric Loader: 0.18.1
• Fabric API: (latest for 1.21.8)
• Firmament:
  • 3.11.0+mc1.21.7 → ❌ crashes
  • 3.9.0 → ✅ works

Expected behavior
Game should start normally with Firmament 3.11.0 and 42.0.0, same as 3.9.0.

Actual behavior
Game crashes during startup at Firmament::onClientInitialize.

错误报告-2025-12-20_17.52.05.zip

Reproduction steps

1. Launch Minecraft 1.21.8 with Fabric
2. Install Fabric API and Firmament 3.11.0
3. Start the game → crash occurs
4. Replace Firmament with 3.9.0
5. Start the game → works normally

Notes

• Modrinth lists Firmament 3.11.0 as compatible with Minecraft 1.21.8.
• This suggests a regression introduced between 3.9.0 and 3.11.0.
• Crash occurs before reaching the title screen.

Logs
I have attached the full crash report and latest.log.

Minecraft Log

[lineargraph]

relevant snippet:

java.lang.RuntimeException: Could not execute entrypoint stage 'client' due to errors, provided by 'firmament' at 'moe.nea.firmament.Firmament::onClientInitialize'!
        at net.fabricmc.loader.impl.FabricLoaderImpl.lambda$invokeEntrypoints$0(FabricLoaderImpl.java:409)
        at net.fabricmc.loader.impl.util.ExceptionUtil.gatherExceptions(ExceptionUtil.java:33)
        at net.fabricmc.loader.impl.FabricLoaderImpl.invokeEntrypoints(FabricLoaderImpl.java:407)
        at net.fabricmc.loader.impl.game.minecraft.Hooks.startClient(Hooks.java:53)
        at knot//fudge.notenoughcrashes.fabric.mixinhandlers.ModLoaders.fabricEntrypoints(ModLoaders.java:9)
        at knot//net.minecraft.class_310.redirect$dga000$notenoughcrashes$catchFabricInit(class_310.java:11579)
        at knot//net.minecraft.class_310.<init>(class_310.java:481)
        at knot//net.minecraft.client.main.Main.main(Main.java:249)
        at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:514)
        at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:72)
        at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
        at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
        at java.base/java.lang.reflect.Method.invoke(Method.java:580)
        at oolloo.jlw.Wrapper.invokeMain(Wrapper.java:112)
        at oolloo.jlw.Wrapper.main(Wrapper.java:105)
Caused by: java.lang.NumberFormatException: For input string: "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@"
        at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:67)
        at java.base/java.lang.Integer.parseInt(Integer.java:648)
        at java.base/java.lang.Integer.parseInt(Integer.java:778)
        at knot//moe.nea.firmament.gui.config.storage.FirmamentConfigLoader.updateConfigs(FirmamentConfigLoader.kt:166)
        at knot//moe.nea.firmament.gui.config.storage.FirmamentConfigLoader.loadConfig(FirmamentConfigLoader.kt:48)
        at knot//moe.nea.firmament.Firmament.onClientInitialize(Firmament.kt:110)
        at java.base/java.lang.invoke.MethodHandleProxies$1.invoke(MethodHandleProxies.java:199)
        at jdk.proxy3/com.sun.proxy.jdk.proxy3.$Proxy79.onInitializeClient(Unknown Source)
        at net.fabricmc.loader.impl.FabricLoaderImpl.invokeEntrypoints(FabricLoaderImpl.java:405)
        ... 12 more

god damn this config system. at which point do i just formalize a config system in a proof assistant that supports compiling to java. for now delete .minecraft/config/firmament to likely fix the issue.