Mod Loader (Required)

Fabric

Minecraft Version (Required)

1.19.2

Mod Version (Required)

4.3.12

Notes (Required)

While closing the game a crash-like message appears in the log. This does not appear to affect anything that I can see but I figured it's worth mentioning. Below is the message found in the log.

[14:18:17] [Render thread/INFO]: Stopping! [B#771] [14:18:17] [Render thread/INFO]: [STDOUT]: Saving config results [B#771] [14:18:18] [Render thread/ERROR]: Calling server config when it is not yet available! This is a bug! Message: Config data is missing [B#771] java.lang.Exception: Config not yet available [B#771] at fuzs.puzzleslib.config.FabricConfigDataHolderImpl.lambda$testAvailable$1(FabricConfigDataHolderImpl.java:45) ~[PuzzlesLib-v4.3.12-1.19.2-Fabric.jar:?] [B#771] at com.mojang.datafixers.util.Either$Right.ifRight(Either.java:109) ~[datafixerupper-5.0.28.jar:?] [B#771] at fuzs.puzzleslib.config.FabricConfigDataHolderImpl.testAvailable(FabricConfigDataHolderImpl.java:44) ~[PuzzlesLib-v4.3.12-1.19.2-Fabric.jar:?] [B#771] at fuzs.puzzleslib.config.ConfigDataHolderImpl.getOrCreateDefaultConfig(ConfigDataHolderImpl.java:70) ~[PuzzlesLib-v4.3.12-1.19.2-Fabric.jar:?] [B#771] at fuzs.puzzleslib.config.ConfigDataHolderImpl.config(ConfigDataHolderImpl.java:59) ~[PuzzlesLib-v4.3.12-1.19.2-Fabric.jar:?] [B#771] at fuzs.puzzleslib.config.ConfigHolder.get(ConfigHolder.java:28) ~[PuzzlesLib-v4.3.12-1.19.2-Fabric.jar:?] [B#771] at fuzs.easyanvils.client.handler.NameTagTooltipHandler.onItemTooltip(NameTagTooltipHandler.java:16) ~[EasyAnvils-v4.0.10-1.19.2-Fabric.jar:?] [B#771] at net.fabricmc.fabric.api.client.item.v1.ItemTooltipCallback.lambda$static$0(ItemTooltipCallback.java:37) ~[fabric-item-api-v1-1.6.6+b7d1888890-62e587ecd66f849b.jar:?] [B#771] at net.minecraft.class_1799.handler$fej000$fabric-item-api-v1$getTooltip(class_1799.java:8662) ~[client-intermediary.jar:?] [B#771] at net.minecraft.class_1799.method_7950(class_1799.java:835) ~[client-intermediary.jar:?] [B#771] at net.minecraft.class_310.method_1485(class_310.java:805) ~[client-intermediary.jar:?] [B#771] at net.minecraft.class_7454.method_43796(class_7454.java:20) [client-intermediary.jar:?] [B#771] at net.minecraft.class_1126.method_4799(class_1126.java:26) [client-intermediary.jar:?] [B#771] at net.minecraft.class_1124$class_7457.method_43807(class_1124.java:61) [client-intermediary.jar:?] [B#771] at net.minecraft.class_1124.method_43804(class_1124.java:42) [client-intermediary.jar:?] [B#771] at net.minecraft.class_310.method_43759(class_310.java:2590) [client-intermediary.jar:?] [B#771] at eu.pb4.polymer.impl.client.InternalClientRegistry.rebuildSearch(InternalClientRegistry.java:422) [polymer-0.2.18+1.19.2-cd67caaa292fd17e.jar:?] [B#771] at eu.pb4.polymer.impl.client.InternalClientRegistry.disable(InternalClientRegistry.java:153) [polymer-0.2.18+1.19.2-cd67caaa292fd17e.jar:?] [B#771] at net.minecraft.class_310.handler$jbi000$polymer$onDisconnect(class_310.java:30000) [client-intermediary.jar:?] [B#771] at net.minecraft.class_310.method_18096(class_310.java:2149) [client-intermediary.jar:?] [B#771] at net.minecraft.class_310.method_18099(class_310.java:2108) [client-intermediary.jar:?] [B#771] at net.minecraft.class_310.method_1490(class_310.java:1060) [client-intermediary.jar:?] [B#771] at net.minecraft.client.main.Main.method_44604(Main.java:260) [client-intermediary.jar:?] [B#771] at net.minecraft.client.main.Main.main(Main.java:51) [client-intermediary.jar:?] [B#771] at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:462) [fabric-loader-0.14.19.jar:?] [B#771] at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74) [fabric-loader-0.14.19.jar:?] [B#771] at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23) [fabric-loader-0.14.19.jar:?] [B#771] Process exited with code 0

latest.log (Optional)

No response

Thanks for the report! This is not a real issue, it's more of a notice for me that there is an invalid access to the Easy Anvils config, but all this is handled. This has been fixed for 1.19.3+, but probably not worth the effort to bring this back to 1.19.2.