New PacketEvents release here!

Finally a new update with a lot of bug fixes & a few additions. This update wouldn't be possible without these contributors ❤️: @SamB440, @AoElite, @Tofaa2, @cheaterSK, @BlueTree242, @joshuaprince, @AbhigyaKrishna, @booky10, @gabber235

Changelog

• Added testing of item tags
• Fix NPCs not spawning on modern versions
• Fix Level NBT missing on enchanted items exception
• WrapperPlayServerScoreboardObjective & WrapperPlayServerUpdateScore fixed on 1.20.3/1.20.4
• Fix Vector3i#subtract
• Addition of VillagerLevel, Rotation, Color and DyeColor
• Fix WrapperPlayServerResourcePackSend in 1.16
• Fix packet re-encoding on Velocity
• Fix certain server listing websites failing to ping PacketEvents servers
• Properly read isFrontText in sign edit wrappers
• Account for an entity eye field in ParticleVibrationData
• Fix GSON component serialization on modern versions
• Correct the maximum durability of ItemTypes.NETHERITE_HELMET
• Fix MojangAPIUtil#requestPlayerTextureProperties(UUID)
• Add new 1.20.4 entity poses
• Addition of WrapperPlayServerActionBar
• Fix player instances being null after a reload
• Fix bStats metrics on velocity module
• Increase AdventureNBTSerialization.DEPTH_LIMIT to 512

Learn how to use 2.2.1 by following our Wiki

Depending on pre-built PacketEvents

Changelog

• Support for 1.20.3/1.20.4 Minecraft (thanks to @booky10 for contributions)
• Initialization Optimization on Spigot
• bStats implemented for Velocity
• bStats implemented for BungeeCord
• EntityMetadataProvider#entityData(ClientVersion) added and EntityMetadataProvider#entityData() deprecated!

Learn how to use 2.2.0 by following our Wiki

Depending on pre-built PacketEvents

Changelog

• Support for 1.20.2
• Minor bug fixes (Channel finding on modern versions, MerchantOffers wrapper, Some Adventure API exceptions)

API Additions

• PacketConfigReceiveEvent, PacketConfigSendEvent
• EntityMetadataProvider interface created, allowing external PacketEvents Addons to provide more advanced abstraction to our entity metadata system

Learn how to use 2.1.0 by following our Wiki

Depending on pre-built PacketEvents

Bug fixes

• WrapperPlayServerChunkData index out of bounds exceptions when used fixed

Learn how to use 2.0.2 by following our Wiki

Summary

Bug fixes

• Sending packets now works on proxies no matter the client version of the target. Just make sure the specific wrapper exists on the target's server version.
• Minor fix to item mappings for versions 1.12 and older
• Added missing constructors, getters and setters for WrapperPlayServerHurtAnimation

API additions

• You can now detect if the current platform is a proxy or not

boolean proxy = PacketEvents.getAPI().getInjector().isProxy();

Learn how to use 2.0.0 by following our Wiki

Thanks for all the support after the 2.0.0 release, here is a patch update, please update to this for the latest bug fixes and features.

Summary

• We now support versions 1.8 - 1.20.1
• We now have partial support for some new platforms such as Velocity and BungeeCord (Sending packets on proxies is still being worked on)
• Our packet wrapper design has shifted from reflection to netty's bytebuffers

Learn how to use 2.0.0 by following our Wiki

Thank you to everyone involved in this update. Finally 2.0.0 is out, from now on we will be releasing minor and patch updates. Thanks to all the users that helped us test 2.0.0 by using the snapshot versions, you should now update to this release.

CHANGELOG

• Added support for 2.0 beta PacketEvents. You can now safely run a plugin shading PacketEvents Beta 2.0.0 and another plugin running 1.8.4 without any issues. There used to be an issue where packets sent by 2.0 would be discarded. (cancelled)
• Deprecated PacketEvents#loadAsync and PacketEvents#loadAsyncNewThread. This "feature" was removed in 2.0, so I decided to deprecate it here. It really made no sense having that.

EXAMPLE USAGE

Example for PacketEvents 1.8.4

CHANGELOG

• Fixed our injector for 1.7.10 servers. Just a little note to the 1.7.10 users... Dear developers, please forward this to your users. Consider updating your server to 1.8.8. There shouldn't be anything holding you guys back from updating your network. Run a 1.8.8 server with ViaVersion & ViaBackwards & ViaRewind to still support 1.7.10 clients if you want. I'm trying to eliminate all 1.7.10 server users. 1.7.10 support might be dropped in future releases in exchange for smaller file size & sustainability. We have to use jars thankfully hosted by funkemunky to support 1.7. If these jars ever get taken down, packetevents would not be able to be built, and we'd abruptly have to end 1.7.10 support.

EXAMPLE USAGE

Example for PacketEvents 1.8.3

CHANGELOG

• Added support for new snapshot versions of ProtocolLib.

Background information

Almost 2 weeks ago, I made an issue on ProtocolLib's GitHub repository. I noticed some flaws in their channel pipeline injector. (In monkey words, how to hack into server code and listen to packets) Thankfully a developer called derklaro improved their injector. This leads to better performance for ProtocolLib.

So why would you care?

If you ever came across a ProtocolLib plugin that modified packets, you'd notice packetevents wouldn't get these modifications. This would lead to player velocity modifying ProtocolLib plugins causing issues, especially for anti-cheats. These snapshot builds of ProtocolLib fix this too. ProtocolLib will always process outgoing packets before us.

EXAMPLE USAGE

Example for PacketEvents 1.8.2

CHANGELOG

• Fixed update checker. All builds of packetevents older than v1.8.1 will now have a broken update checker. (if it were enabled) Us now following semantic versioning breaks this. Good side is our current new update-checker will work for the future releases (including 2.0)

EXAMPLE USAGE

Example for packetevents 1.8.1