[CRASH] <title> Crash at mod initialization

Question

[CRASH] <title> Crash at mod initialization

Closed this issue 3 months ago · 9 comments

Galysso commented 5 months ago

Minecraft Version

1.21.1

Mod Version

21.1.53

Mod Loader

Fabric

What environment are you running the mod in?

Client

Issue Description

I have a relatively small modpack yet. When I have more time I can try with a smaller set of mods to try to identifiy which mod might be incompatible.

I provide two crash reports : one with all my modpack, another one with fewer tooltips mods.

Crash Log

crash-2025-04-10_08.58.56-client.txt

crash-2025-04-10_09.04.30-client.txt

Are you doing anything weird?

No response

Kyoshiku-SP · Answer 1 · 2025-04-10T22:42:33.000Z

Same, I experienced this when I was trying to connect to the server with Velocity

Darkhax · Answer 2 · 2025-04-11T21:54:57.000Z

Thank you for reporting this issue Galysso, I am looking into it now and should hopefully have a fix available for you soon.

Darkhax · Answer 3 · 2025-04-11T22:24:03.000Z

I've released a new update which should prevent Bookshelf from crashing here. This issue is actually unrelated to Bookshelf though, you have two mods adding new item rarities with the name none which is very wrong. Newly created enum values should always have the name of the mod added for the sake of identification and to avoid conflict errors like this one.

When you run the game with the new version installed it will print an error message that looks something like this.

Duplicate name '{}' found in enum '{}'. Another mod is doing something very wrong. old='{}' new='{}'

I've included all of the available information to help you track it down, but rarity doesn't have much in terms of identifying info so I don't know how much it will help. While this update may prevent Bookshelf from crashing, this is a serious issue and anything else that tries to read item rarity will probably blow up.

https://www.curseforge.com/minecraft/mc-mods/bookshelf/files/6412566

Horizoll · Answer 4 · 2025-04-13T15:56:38.000Z

Hello,

I had few crashes with a new version of bookshelf, it doesn't happen with [21.1.53] version

crash-2025-04-13_20.30.16-client.txt
crash-2025-04-13_09.43.50-client.txt
crash-2025-04-13_10.03.51-client.txt

Darkhax · Answer 5 · 2025-04-13T17:57:29.000Z

@Horizoll Hello, why do you think Bookshelf is related to the crashes? You've uploaded three unique crashes which all appear to have nothing to do with this issue or Bookshelf.

Crash 1: Distant Horizons having trouble reading a save folder name
Crash 2: Fabric failing to load registries on the title menu, likely related to another mod.
Crash 3: Sparkweave crashing when a fishofthieves:wildsplash was ticked.

Horizoll · Answer 6 · 2025-04-14T03:40:49.000Z

I simply replaced old version [21.1.53] with a new one [21.1.56] and got some troubles.

I checked every mod i updated, i got no crash with old version of bookshelf.
Right now, if i replace it with a new one, i got distant horizons related crash that was updated 9 days ago.

SteveKunG/FishOfThieves#65

I mistakenly thought it was Sparkweave <=> FishOfThieves issue, but it is not.

Horizoll · Answer 7 · 2025-04-14T04:11:35.000Z

There is a modpack i use, it is already contains both versions of bookshelf to pick one over another.

https://www.dropbox.com/scl/fi/6x7a4xbi3tt82xhuw3ei4/Mods14.04-BookShelf-x2.7z?rlkey=jdvx3yiyc59zyo1wxi49v3yw9&e=1&st=2d89454v&dl=0

Horizoll · Answer 8 · 2025-04-14T08:43:57.000Z

I removed some over-extra mods and [1.21.1] build with [21.1.56] BookShelf started to work without crashes, hopefully.

There is a list of these mods:

Additionally after that i removed:

Lets Do API 1.3.0
https://modrinth.com/mod/do-api
Lets Do Vinery 1.5.0
https://modrinth.com/mod/lets-do-vinery

jocelin-cailloux · Answer 9 · 2025-04-14T09:55:34.000Z

Thank you for reporting this issue Galysso, I am looking into it now and should hopefully have a fix available for you soon.

Hey. Late reply but thank you a lot for your reactivity :-)

And in reply to your comment, that is absolutely possible that one of my mods added a rarity called "none". But I ended up removing my former rarity mod and coded my own because this was not the only issue I found.

Share to