Describe the bug
On Minecraft 1.21.1 (NeoForge), the Carry On mod causes a hard server crash when a player attempts to pick up a vanilla chest.
The crash occurs synchronously inside the server tick loop, resulting in a full server shutdown (not a soft disconnect or player-only crash). Once triggered, the server must be manually restarted.
This issue has been reliably reproduced and isolated to Carry On. Removing the Carry On mod resolves the crashing behavior, and the crash can be reintroduced by re-adding the mod, followed by picking up a chest again.
...
To Reproduce
Steps to reproduce the behavior:
- Start the Server
- Install Carry On
- Join the server
- Place a vanilla chest
- Attempt to pick up the chest using Carry On
...
Game Information:
- Minecraft Version: 1.21.1
- Mod Loader: NeoForge 21.1.209
- Carry On Version: 2.2.4.x (NeoForge build)
...
Additional context, logs:
Environment:
- Dedicated Linux server (headless)
- Java 21 (Amazon Corretto / OpenJDK)
- ~100 installed mods (large modpack)
The crash originates, as far as I can see, from Carry On’s server tick handling, specifically during logic that evaluates the carried object’s state.
...
Observed stack trace characteristics:
Exception in server tick loop
java.lang.ArrayIndexOutOfBoundsException
Triggered during CarryOnCommon.onCarryTick(...)
Failure occurs while serializing or iterating NBT data (CompoundTag.toString() / StringTagVisitor)
Crash propagates up the tick loop, terminating the entire server process
This strongly suggests an NBT handling / container data edge case when Carry On attempts to process a TileEntity-backed container (e.g., chest) under NeoForge 1.21.1.
Describe the bug
On Minecraft 1.21.1 (NeoForge), the Carry On mod causes a hard server crash when a player attempts to pick up a vanilla chest.
The crash occurs synchronously inside the server tick loop, resulting in a full server shutdown (not a soft disconnect or player-only crash). Once triggered, the server must be manually restarted.
This issue has been reliably reproduced and isolated to Carry On. Removing the Carry On mod resolves the crashing behavior, and the crash can be reintroduced by re-adding the mod, followed by picking up a chest again.
...
To Reproduce
Steps to reproduce the behavior:
...
Game Information:
...
Additional context, logs:
Environment:
The crash originates, as far as I can see, from Carry On’s server tick handling, specifically during logic that evaluates the carried object’s state.
...
Observed stack trace characteristics:
Exception in server tick loop
java.lang.ArrayIndexOutOfBoundsException
Triggered during CarryOnCommon.onCarryTick(...)
Failure occurs while serializing or iterating NBT data (CompoundTag.toString() / StringTagVisitor)
Crash propagates up the tick loop, terminating the entire server process
This strongly suggests an NBT handling / container data edge case when Carry On attempts to process a TileEntity-backed container (e.g., chest) under NeoForge 1.21.1.