Hi,
I’ve run into a conflict between CraterLib and the GoProne mod on Minecraft 1.18.2 (Forge 40.3.11).
When both CraterLib and GoProne are installed with a few other mods that never caused that specific issue, the server logs the following error whenever a player die's:
java.lang.NullPointerException: PlayerProneData capability not attached!
at alpvax.mc.goprone.network.SetPronePacket.lambda$handle$0(SetPronePacket.java:30)
at net.minecraftforge.common.util.LazyOptional.orElseThrow(LazyOptional.java:281)
-
Removing CraterLib fixes the issue immediately (GoProne works fine).
-
With CraterLib present, it seems GoProne’s PlayerProneData capability is never attached to the player.
This only happens when both mods are loaded together.
Setup:
Minecraft: 1.18.2
Forge: 40.3.11
GoProne: 2.2.1
CraterLib: 2.1.5
Could you check if CraterLib is interfering with capability attachment on players?
Thanks a lot for your work on this mod!
Hi,
I’ve run into a conflict between CraterLib and the GoProne mod on Minecraft 1.18.2 (Forge 40.3.11).
When both CraterLib and GoProne are installed with a few other mods that never caused that specific issue, the server logs the following error whenever a player die's:
Removing CraterLib fixes the issue immediately (GoProne works fine).
With CraterLib present, it seems GoProne’s PlayerProneData capability is never attached to the player.
This only happens when both mods are loaded together.
Setup:
Minecraft: 1.18.2
Forge: 40.3.11
GoProne: 2.2.1
CraterLib: 2.1.5
Could you check if CraterLib is interfering with capability attachment on players?
Thanks a lot for your work on this mod!