-
Notifications
You must be signed in to change notification settings - Fork 50
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
Crash with clientcommands - LockedSlotKeeper assumes container doesn't change #324
Comments
Yeah |
Oh my lord, the reason for the crashes was the version difference, updating libIPN and Inventory Profiles Next solved the issue |
Well I'm happy it's fixed 😁 I have the new version spam on startup for a reason 🤣 edit Well it sounded too good lol |
Yeaaaah, I was kinda afraid that it wasn't going to be easy... do you want to chat on Discord so we're not clogging Github? |
yeap |
Alright |
Soo the cause was pinned down to.... drumroll... the server being paper. |
"Fix/Workaround" will be available in the next release. However 1.19.3 is no longer supported and will not receive the fix. |
Hi, I've looked briefly into a crash reported to clientcommands here and I think there is an issue in
LockedSlotKeeper
where it implicity assumes the container doesn't change by storing some slot ids, although I didn't fully understand what's going on yet. Clientcommands changes the open container when a container GUI is opened here. I was wondering if you could provide some insight into what's going on?To reproduce, install clientcommands and inventory profiles next, join a world, place some dirt in a chest, then type
/cfinditem dirt
into chat.The text was updated successfully, but these errors were encountered: