Skip to content
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

Crashes on startup (Canary) #17

Open
Attikittyalt1 opened this issue Dec 30, 2022 · 1 comment
Open

Crashes on startup (Canary) #17

Attikittyalt1 opened this issue Dec 30, 2022 · 1 comment
Labels
bug Something isn't working external This is triggered by something outside our control

Comments

@Attikittyalt1
Copy link

https://pastebin.com/xUs9wLtg

@amadornes
Copy link
Member

Thank you for your report!

This looks like an incompatibility with Canary, and there seems to be at least one issue open in their repo about the same issue, but with another mod: AbdElAziz333/Canary#69.

Vanilla has a reusable state system currently shared by blocks and fluids. SCM also uses it for circuit components.
Canary is trying to optimize the vanilla cases, but it seems to catch fire if the state belongs to anything else it doesn't know about.

Unless/until it gets fixed on their end, your best option for the time being would be to disable Canary, or, if it has a config option to disable its state optimizations, to disable them.

From a technical standpoint, updating Canary to supports custom state holders doesn't look very hard, but I guess it's more of a question of whether that would still result in a performance improvement, and whether AbdElAziz is still actively developing for 1.18 or not.

@amadornes amadornes added bug Something isn't working external This is triggered by something outside our control labels Dec 30, 2022
@amadornes amadornes changed the title Crashes on startup (I think it's with REI) Crashes on startup (Canary) Dec 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working external This is triggered by something outside our control
Projects
None yet
Development

No branches or pull requests

2 participants