There seems to be an issue when converting lapis into source gems.

Steps to reproduce:

1. Place lapis in imbuement chamber with a source jar nearby.
2. Crash

The issue here is that when this happens, you cannot join the server again until the recipe is done cooking.

The exact thing that pops up when you get disconnected is this:
"Internal Exception: io.netty.handler.codec.DecoderException: java.lang.ArrayIndexOutOfBoundsException: Index 64 out of bounds for length 7"

Here are the server logs:
client-latest.log
server-latest.log

Update: It seems to do it only if there's source jar near by.

We've run into this as well across ~30 players, there doesn't seem to be any consistency on who is affected, be it ops, gamemode, shaders. The problem pretty consistently follows the same ~50% of players even after client and playerdata wipes.

There are a couple things that cause the disconnects that we've observed.

• Source Jar being next to Imbuement chambers as listed initially
• Drygmy summoning with a drygmy henge
• Certain glyphs scribe table

Unaffected players are able to break the offending blocks and the affected ones are promptly able to join again.

Bump, very similar issue. Only non-op players rendering chunks that are using source jars to produce magic (especially making essence) get kicked. I'm op and it does not kick me. But anyone on my server trying to make essence gets kicked immediately when they begin the creation of the essence.

Ars Nouveau - Things that cause chunk crashes

Depleting Source Jars
Examples:
Hooking up a source jar to an enchanting Apparatus (which depletes it)
Ritual Braziers which require a source connection (which depletes it or requires an active connection)
Drygmy Farms (which depletes it)

Other:
-Jar of Containment on an archevoker creates a lag machine and will exist when you hold or look at it

Please update both bumblezone and Ars Nouveau to latest, a fix has just been uploaded.