-
Notifications
You must be signed in to change notification settings - Fork 31
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
Breaking generic chests #52
Comments
We are experiencing the same issue, version 8-0.0.12.zip. It doesn't appear to be all generic oak chests, just some in specific areas. No crash report, no server logs, just the regular disconnected messages. |
3 different players. Empty chest, but not sure if that matters, 100% repeatable. |
Experiencing the same on my server. Version 8-0.0.14. Seems to be just generic chests. Repeatable, and just crashes client out with no error message. |
Same errors are happening in our community server as well with chests, waystones and different TP commands as well!! |
@InFuRiTy This one seems to have nothing to do with the random game close ones. Allthough here the removal of rubidium could help that's not a real solution cause rubidium is pretty essential for middle to lower end pcs running this pack. |
Updating to 8.0.0.14 fixed this for us. |
Only found it on 8-0.0.14. More testing tonight show it is just generic chest that are effected and not Quark chests. |
I can confirm that it was only the generic chests. However, a client and server side update allowed me to pick up the generic chest. Not sure what the client difference is there; wish it gave a crash report. We're treating these like super advanced mimics. |
@whatthedrunk can be closed, last change of config in 0.1.3 fixed this problem |
So, in a previous patch placing generic chests would cause a game crash with a crash report.
In the latest version, attempting to break generic chests causes the game to close down immediately, without producing any form of crash report, and didn't even bring the launcher back up upon closing.
The text was updated successfully, but these errors were encountered: