Open ToneyFoxxy opened 3 weeks ago
Workaround:
Add the line
mixin.minimal_nonvanilla.world.block_entity_ticking.support_cache=false
to the lithium.properties in the config folder in the minecraft folder.
Workaround: Add the line
mixin.minimal_nonvanilla.world.block_entity_ticking.support_cache=false
to the lithium.properties in the config folder in the minecraft folder.
Still crashes https://gist.github.com/ToneyFoxxy/e3cff8f8372d69bb8c0599b3ec41835f#file-gistfile1-txt
Also crashes on my brother's PC which is running Endeavour OS
I have the same problem I'm playing on MacOS and with PrismLauncher, is crash with the lithium 0.13 for minecraft 1.21, but with the version of Lithium 0.12.7 the game is working without a problem.
this is my crash file. crash-2024-08-21_20.04.19-client.txt
Workaround: Add the line
mixin.minimal_nonvanilla.world.block_entity_ticking.support_cache=false
to the lithium.properties in the config folder in the minecraft folder.Still crashes https://gist.github.com/ToneyFoxxy/e3cff8f8372d69bb8c0599b3ec41835f#file-gistfile1-txt
@ToneyFoxxy, try also adding this line to the config:
mixin.block.hopper=false
https://github.com/CaffeineMC/lithium-fabric/blob/1.21/lithium-mixin-config.md#mixinblockhopper
@ClassyElm That one works on it's own, thanks
Can confirm on 1.21.1-0.13.0. Same crashes with only Lithium installed. Had to disable both mixins mentioned above.
Running Ubuntu 24.04 on the default kernel, if that helps.
I think some users had this issue when changing their game version without creating a new profile in their custom minecraft launcher. It is currently unclear why this issue happens
I did upgrade Minecraft in-place from 1.21.0 to 1.21.1. Will try to recreate a profile when i get back to my computer next wednesday
Ideally when you do something like that it's good to check it works on the officially supported version before creating an issue on GitHub.
I don't think it is expected that changing the version in a minecraft launcher behaves differently from creating an equivalent profile with the new version
i
I think some users had this issue when changing their game version without creating a new profile in their custom minecraft launcher. It is currently unclear why this issue happens
seconded, updating in place instead of new profile causes crash however fresh instance does not cause a game crash
Fixed my issue as well. Works on fresh profile. It wasn't to much hassle to pull over my xaeros maps and a few other UI mod configs and I'm good now.
Version:
Reproduction Steps:
Crash Report File:
Additional Information: