search

OhHeyItsJosh / Elytra-Physics

A simple mod that adds cape-like physics to the elytra when worn by the player.
MIT License
0 stars 0 forks source link

Version 2.0 Causes Crashes (1.20.1 fabric) #2

Closed Shadowpudding closed 1 week ago

Shadowpudding commented 10 months ago

Version 2.0 Causes Crashes for me. At first it always appears that another mod is cusing it but after scrolling and testing I found that this mod causes it. It might be in conjunktion with other mods, but because of the aforementioned issue testing would take a long time. The previous Version works though. I do have more reports that show the same issue. crash-2023-10-31_00.13.31-client.txt

OhHeyItsJosh commented 9 months ago

Hmm, while the crashlog mentions ChocoCraft, it appears to work fine with ChocoCraft. Another person mentioned that it crashes when the Origins mod is installed in Forge. After testing, it appears Origins it is also incompatible in Fabric.

I will have a look and see if I can find why the Origins mod is causing a mixin injection failure.

Shadowpudding commented 9 months ago

I would assume that that might be because of the origin Elytrian because that technically uses an elytra while not having one equipped, so that might be an issue. Tomorrow evening I could do some more testing since I also use the origin mod, but at least one other mod I use could cause the issue.

HaXrBOT commented 6 months ago

Hope that you get the chance to look into this soon(tm), as i would love to have the effect from this mod on modded Elytras too. I get a similar looking crash report to the one sent by Shadowpudding, so thought that i would share it here in case it helps you somehow.

crash-2024-03-09_16.56.51-client.txt

Trynthlas commented 2 months ago

Similar crash: https://mclo.gs/LZLetbL This one is specifically calling out Supplementaries, but that may just be a loading order thing.

Origins is installed, due to wanting to play with Origins: Wither Unleashed

OhHeyItsJosh commented 1 week ago

Apologies for the long wait, This should now be resolved in the latest version (2.1).