Needs to be updated 1.21.11

[Father-Fat-Goose]

As already mentioned in the title, update it to 1.21.11

P.S.
Really good plugin, but isn't there a way to be less dependent on constant updates? I admit I'm not good at creating plugins for MC, but I have several plugins that were created almost 11 years ago, and they work on the latest version, looking at the new "modern" counterparts that have replaced them, it seems that developers used to work really better.
Ok, wait. I'm not saying that your plugin is bad, no, it's really good, and that's why I decided to write about it. I think it would be better if I were less dependent on updates, if that's possible. Developer is a simple person who has a personal life and his own problems, after all, he simply does not have to constantly monitor updates. So if this plugin doesn't update after the next MС update, it will be very sad. (I hope you haven't abandoned it).

[KaspianDev]

Update is in progress.

Packets are a low level thing in case of developing minecraft plugins. Due to how the game's protocol breaks every update every plugin relying on it must update. You have probably noticed the need to update protocollib on every update that isn't tiny (fixing a bug or two). Most plugins can work using the spigot api alone but for certain edge cases like this, it's better to use packets. Similar plugins to antipopup that use spigot api often have incompability issues with other plugins.

[rudde0]

ProtocolLib has initial build for 1.21.11

[aokod]

Really good plugin, but isn't there a way to be less dependent on constant updates?

Yes, absolutely. In fact, the v1.21.11 module itself should work on Paper 1.21.11 servers as-is. Looking at the plugin's code, the actual PlayerInjector module has not changed since 1.21.6 or so.

The Spigot API used a mapping system to provide readable names for native server functions when official mappings weren't available. Paper started using a Mojang-mapped runtime with version 1.20.5 and Spigot 26.1+ will be using Mojang mappings as well.

I am willing to go out on a limb and suggest that the plugin's usage of Spigot mappings up until this point is one of the primary reasons for the delay in updates. As mentioned by #129 (comment), the Spigot reobfuscator is bottlenecked by how quickly the Spigot development team is able to review each change to the mappings data, which occurs with just about every new version.

See my PR draft #130 for more context.

[mrfloris]

spigot has the .4 release for mc 1.21.11

[KaspianDev]

Released, moving the mapping change to 26.1 release as spigot is the primary target server.