Dan Mulloy

@Ultra03 it looks like the old examples have vanished (likely to do with curse forge redoing their website). The gist of it is that the old API was a lot...

This looks to be the same issue as https://github.com/dmulloy2/ProtocolLib/issues/36. Can you set `debug=true` in the server.properties and `debug: true` in the ProtocolLib config? It should print out a (more) helpful...

That code didn't seem to work. I modified it a bit [here](https://gist.github.com/dmulloy2/5d52ddbb89a1609dbea2) and didn't get any CME's.

Any more info on this?

I'd like to get this fixed before releasing 3.6.5, can I get the debug info?

It could be a race condition, but ProtocolLib _should_ hold on to the packet until you're finished modifying it. It's likely that the CME is internal (PL or Minecraft itself),...

Any more information on this?

seems to be NBT that isn’t properly cloned and getting modified on different threads. @Protonull or @Kneesnap can one of y’all provide some code?

@Kneesnap Try cloning the NBT tag before modifying it. My guess is that the same instance is getting passed around and the netty threads don't like the concurrent modifications.

interesting. does this happen in listeners or just when creating?