-
Notifications
You must be signed in to change notification settings - Fork 0
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
Quark Storage Crate items disappear #2
Comments
Turns out to be a conflict between Quark, C2ME and Smooth Chunk. I have created an issue here: github.com/VazkiiMods/Quark/issues/5132
|
It turns out that I can also reproduce the bug if I use: |
edit: I have further narrowed the scope and can now consistently reproduce the bug in an dedicated server <-> client environment, but reducing the mod list. Minecraft ModsInstall on Client and serverQuark Dependencies Install on Server onlyConcurrent Chunk Management Engine (Fabric) (aka C2ME) Dependencies Why am I posting this as a Quark issue?Because it is ONLY the Quark
Somehow quark handles it gracefully for other Quark interactive blocks. My hope is that the Storage Crate can have the same graceful behavior - even if the root of the problem should be a conflict between the other mods. Quark do not have the responsibility to fix bugs for other mods, but it seems like Quark already have a working solution at hand in those other interactive blocks, so the fix is potentially easy to do (maybe? 😬) How to reproduce
What was expected: The item to be in the Storage Crate Workaround: Removing Observation: Even when items are placed in a world while C2ME was not installed, then as soon as one stops the server with C2ME installed (even without making any changes to the world) the items disappear from the Storage Crate. Log:
|
Minecraft 1.20.1
Forge
Quark have a conflict with some other mod, where the content of Storage Crates is wiped.
When the server is closed the items does not appear in the region files.
When Quark is alone on the server the issue does not appear.
The text was updated successfully, but these errors were encountered: