You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happens?
Getting the Hardlight Shield into your inventory will crash your game, if you have Good Ending mod installed.
How do I cause it?
Have both the Ori mod and the Good Ending mod installed, and give yourself the Light Shield. Boom! Crash.
Is this bug so bad that you find it nearly impossible to play?
Nope. But the moment you acquire the shield, your own hope to get back into the save again would be to use the NBTEditor.
This is a bug in Good Ending itself. I have taken the liberty of moving this report to their repository on your behalf as I did some reading in their source code to isolate the cause with the help of your crash log. You can check the issue's status here: Good Ending :: Issue #7). As such, this issue will be closed.
After having a look at their source code, you should be able to bypass this issue by giving yourself a shield that has a tag on it. You can use the /give command like this to fix the bug: /give @s orimod:light_shield{Damage:0}
Admittedly, part of this issue is caused by the lack of a Damage field on the Hardlight Shield, which is part of why it is indestructible (adding the tag alone will not help). This will be fixed in the next update of my mod, but this is your workaround for now. I will file a new issue myself for this problem, so no worries about doing that.
What happens?
Getting the Hardlight Shield into your inventory will crash your game, if you have Good Ending mod installed.
How do I cause it?
Have both the Ori mod and the Good Ending mod installed, and give yourself the Light Shield. Boom! Crash.
Is this bug so bad that you find it nearly impossible to play?
Nope. But the moment you acquire the shield, your own hope to get back into the save again would be to use the NBTEditor.
Log file
crash-2023-01-29_14.33.32-server.txt
crash-2023-01-29_14.33.35-client.txt
The text was updated successfully, but these errors were encountered: