"Enchantment Unbreaking is not valid in current registry set" - 8.0-aIpha.3

[JustJum11]

Description

Every so often, in-game I get the following popup:

And it dumps the entire chat history in latest.log. Seems to be similar to #246 but it gives the error for a different reason.

How to reproduce

It seems to happen almost every time Chat Patches attempts to save the chat history. Unfortunately, I only have this issue happen in my main instance, and have been unable to reproduce it in a fresh instance. However, I tried removing every mod other than Chat Patches (+dependencies) in my main instance and the issue still happens.

Expected result

I expect to not get that popup, and for the entire chat history to not be dumped in the log. (Because with thousands of lines of chat being pasted multiple times, the log becomes a pain to read, and could be a security issue if the log is shared online).

Log file link

https://mclo.gs/4jGDWZ9 (I replaced the chat history dump with "[DUMPS ENTIRE CHAT LOG HERE]")

Specs and Details

Required information:

• Computer OS: Windows 10
• Mod version: 8.0-aIpha.2
• Fabric: 0.16.14
• Fabric API: 0.129.0
• YetAnotherConfigLib: 3.7.1
• Mod Menu: 15.0.0-beta.3

(Everything is on latest version)

chatpatches.json

[mrbuilder1961]

this seems like #180 again 😣 do you have the chat log save interval set to anything >0?

[JustJum11]

I tried both 0 and and an interval of 5 and the issue happens regardless.

[mrbuilder1961]

• can you send the chatlog.json file from the broken and normal instances via pastebin or sm?
• does this happen on singleplayer, multiplayer, or both?
• if multiplayer is it only on a certain server?
• what have you been doing when the errors pop up?

[JustJum11]

Here's the chatlog from the instance where I have the issue: chatlog.json. I only use Chat Patches in this one instance anyway. I don't get the issue if I add Chat Patches to a new instance, but the chatlog would be empty there anyway.

It happens on both singleplayer and multiplayer, on every world I've tried so far.

I tried literally just sitting there doing nothing and I still get the errors. (It does seem like I still need to send at least 1 message to trigger a save when waiting for an interval, so I send 1 message). HOWEVER, it doesn't happen in the first world I join after launching the game... ie:

• I launch the game.
• Join a world.
• And I can wait for as long as I want, allowing it to save the chat log as many times as it wants (I can see in Minecraft's log), and never get the error.
• Leave the world, and join a world.
• Then from this point, any time it saves the chat log (Either by waiting for the next interval, pausing with an interval of 0, or leaving the world), I get the error. (I still get errors even if I rejoin again)

So it seems for whatever reason it doesn't give errors if it saves the chat log in the first world I join for the session.

[leonardvdj]

Hello, tagging on to say I'm having the same issue. Consistently reproducible on 1.21.5 with these steps:

• Create a new 1.21.5 fabric instance in Modrinth (Confirmed it happening with .2 on Prism as well)
• Install chat patches 8.0-alpha.2 or 8.0-alpha.3
• Create a new world with cheats enabled
• Give myself an elytra with unbreaking 3 using /give @p elytra[enchantments={unbreaking:3}]
• Exit the world, it will save the log correctly here
• Open the world again
• Write anything in chat and pause the game to save the log, it will now fail with the same error log as OP

OS: Windows 10 Mod Version: 8.0-alpha.2 or 8.0-alpha.3 Fabric: 0.16.14 Fabric API: 0.128.1 Mod Menu: None

If it looks different I can make a separate issue, just wanted to tag on here first as it seemed to be the same error. latest.log 8.0-alpha.2 chatlog 8.0-alpha.2

latest.log 8.0-alpha.3 chatlog 8.0-alpha.3 chatlog_dump_2025-07-28_02.13.54 8.0-alpha.3

[mrbuilder1961]

thanks so much for the detailed breakdown! i'll try to reproduce this when i can

[mrbuilder1961]

i assume this is still reproducable on alpha.4 ?

[JustJum11]

Yep. I followed the same steps as leonardvdj provided above, with alpha.4:

latest.log chatlog.json chatlog_dump_2025-08-06_18.30.01.json

[KozukiYOMA]

I think it's probably the same problem. In my case, it occurred with fire_aspects. latest.log

[mrbuilder1961]

haven't had time recently to work on this but i have one or two ideas to try. in case it wasn't obvious, simply disabling the chat log will stop this from happening, so if you arent dead set on using it that can hold you off until then