Mod loader

NeoForge

Minecraft version

1.21.1

Mod version

15.10.1

Modloader version

NeoForge 21.1.186

Modpack info

[IMPORTANT] If bug:

• I have confirmed this bug is reproducible on a minimal setup, not a modpack with many other mods.

[IMPORTANT] If bug: The latest.log file, not the crash report

https://pastebin.com/y7FhLZzg

Issue description

Easy to reproduce, place a trapped chest in survival and it will turn into a normal chest and inevitably break Jade.
Can be reproduced 100% of the time, only Jade was used in this testing environment.

Jade should not alter the placed block itself and only affect the tooltip. Placing a trapped chest in creative works as intended.

It's not a bug. It's a feature

So you're telling me that Jade throwing actual errors is a feature? Sorry but I can't accept that as answer. It's an actual error message and Jade generates it's own log "JadeErrorOutput.txt". If it was just the Chest being "wonky" without any errors in the log I wouldn't have opened an issue.
I am well aware of the trapped chest being shown as a normal chest is a feature with Jade which is why I have been using it. However, Jade throwing an actual error because of a Null-Reference is definitely not a feature and clearly a bug. More so it's an actual Null-Reference on the container itself when Jade tries to display the contents in it's tooltip so I urge you to look at that problem.

You are right. I will look into it later

Might as well add that I ran into one instance of a lava-filled cauldron also throwing an error but I haven't been able to reproduce this one in an instance with only Jade installed yet. Not sure if this might even be the same cause. Anyways, should I manage to reproduce that one I'll provide a log as well as steps to reproduce it.