https://paste.ubuntu.com/p/956t6VFTMR/

Reproduce without plugins please. So many spigot plugin modifications in that stack.

Reproduce without plugins please. So many spigot plugin modifications in that stack.

I added the protocolib plugin, is this a problem with this plugin?

The server developer suggested that I remove this plugin, but I need it

It may take a long time to remove all plugins and wait for this issue to happen again

I use machine translation, I do n’t speak English, sorry

Astral sorcery does not support any environment outside of normal Forge. This includes things like spigot that modifies underlying code, Sponge, anything like that.
When calls don't function the way they're supposed to in Forge, things can get squirrelly. Especially because protocollib modifies a whole bunch underlying things with the claimed intent of making things run faster. Things don't run faster because you take shortcuts, they run faster because the base code is efficient in the first place. Minecraft has issues in this regard.

So yes, effects of protocollib is all throughout that stack trace, and that it's an error for a concurrent modification exception on the network stack, which is something that protocollib heavily modifies, is the problem. If it can't be reproduced without spigot, or sponge, or anything else you may decide to put in there after pulling protocollib, it's really not an astral sorcery issue and should be taken to the dev of those instead.

Astral sorcery does not support any environment outside of normal Forge. This includes things like spigot that modifies underlying code, Sponge, anything like that.
When calls don't function the way they're supposed to in Forge, things can get squirrelly. Especially because protocollib modifies a whole bunch underlying things with the claimed intent of making things run faster. Things don't run faster because you take shortcuts, they run faster because the base code is efficient in the first place. Minecraft has issues in this regard.

So yes, effects of protocollib is all throughout that stack trace, and that it's an error for a concurrent modification exception on the network stack, which is something that protocollib heavily modifies, is the problem. If it can't be reproduced without spigot, or sponge, or anything else you may decide to put in there after pulling protocollib, it's really not an astral sorcery issue and should be taken to the dev of those instead.

Thank you for your reply. I see