-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server Crash with More Chest Variants #31
Comments
That is odd. I am unsure exactly what I could do about this, have you made an issue on the Ledger mod about this? |
Yes, I made an issue on the Ledger mod about this Issue |
Ah sorry, I opened a Discord Issue, and i have referenced the #302 issue, since other players have same issues with other Chest mods |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
"Describe the bug
When MoreChestVariants and Ledger are installed together on a Fabric server, interacting with a double chest (any variant from MoreChestVariants) causes the server to crash. The crash occurs due to a NullPointerException in Ledger’s ItemRemoveCallback.kt when the pos parameter returns null.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The server should handle inventory transactions without crashing. The expected behavior is for Ledger to log the item change and for the chest to function normally. Instead, the server crashes due to a null value for the block position (pos) in Ledger’s callback.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions (please complete the following information):
Additional context
Crash Report: https://pastebin.com/sA57GKRF
"java.lang.NullPointerException: Parameter specified as non-null is null: method com.github.quiltservertools.ledger.callbacks.ItemInsertCallback$DefaultImpls.EVENT$lambda$1$lambda$0, parameter pos
at knot//com.github.quiltservertools.ledger.callbacks.ItemInsertCallback$DefaultImpls.EVENT$lambda$1$lambda$0(ItemInsertCallback.kt)"
*please fill out as much information as possible. If any required fields are missing, the issue may be closed without any comments.
The text was updated successfully, but these errors were encountered: