Minecraft Version

1.20.1 (LTS)

Mod Loader

Forge

Describe the Issue

The game will crash during launching progress after updating Balm to 7.3.21 from 7.3.20.

Logs

.minecraft/logs/latest.log: https://mclo.gs/UGktSEx
.minecraft/crash-reports/crash-2025-03-23_16.31.05-fml.txt: https://mclo.gs/fDPXXal
.minecraft/crash-reports/crash-2025-03-23_16.32.56-client.txt: https://mclo.gs/0t8AbxT

Can also confirm.
I'm not sure, but key:Lcom/mojang/blaze3d/platform/InputConstants$Key doesn't seem logical, could it be key:com/mojang/blaze3d/platform/InputConstants$Key without the L that should be used?
As in key:com/.. instead of key:Lcom/.. ?

Can also confirm. I'm not sure, but key:Lcom/mojang/blaze3d/platform/InputConstants$Key doesn't seem logical, could it be key:com/mojang/blaze3d/platform/InputConstants$Key without the L that should be used? As in key:com/.. instead of key:Lcom/.. ?

I noticed this in my logs too and had a similar thought, but it's been a hell of a while since I did any Java.

I'm not sure, but key:Lcom/mojang/blaze3d/platform/InputConstants$Key doesn't seem logical, could it be key:com/mojang/blaze3d/platform/InputConstants$Key without the L that should be used? As in key:com/.. instead of key:Lcom/.. ?

L is the prefix for class types in Java signatures, it's correct in this case.

The actual issue was that for some reason the refmap was not being included in the built Kuma jar, which magically fixed itself after switching to ModDevGradle's LegacyForge instead of ForgeGradle.

(...) which magically fixed itself after switching to ModDevGradle's LegacyForge instead of ForgeGradle.

Forge/Gradle things 🤦, smh
Still, good work 💪🔥

also getting this. something related to kuma api