2.11.2+velocity
Compatibility
Changes
PacketEvents 2.11.2 is finally out! 🎉
This update fixes various bugs. It's encouraged that users update. Again, huge thanks to all users who have donated their hard-earned money to PacketEvents since the previous release. It's been received & it's very much appreciated.
Recent donors: PebbleHost, SSomar1607, ipavdev, Meed, frap
Also, thanks to the contributors that made this update possible.
If you intend on donating and do not wish to be mentioned, please add such a note on your donation.
Announcement 📢⚠️
Visit our website: https://packetevents.com
Documentation: https://docs.packetevents.com
JavaDocs: https://javadocs.packetevents.com
I've released a new YouTube video.
What's Changed (Summary)
- Fixed SynchronizedRegistriesHandler issues
- Fixed various equality/nullability issues with Registry values
- Explicitly specify 'Locale#ROOT' for all String#toLowerCaser() calls
- Removed 'end skylight' for 1.21.8 and below
- Log warning message when failing to uninject from velocity initializer
- Recommend release builds (and fallback to development builds) to users who run outdated software.
- Add 'CHAIN' to the 'CHAINS' tag
- Add new offset(Blockface face, int i) method to Vector3f/d/i classes
- Fixed 'infiniburn' tag parsing for 1.18.1 and older
- Fixed unexpected NPE if bukkit entity is null during unsafe lookup
View Full Changelog: https://github.com/retrooper/packetevents/compare/v2.11.1...v2.11.2
If you want to support PacketEvents, consider donating to us on PayPal or sponsoring us on GitHub Sponsors.
Maven/Gradle Dependency Setup Guide
Check it out: https://docs.packetevents.com/introduction/development-setup/
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| packetevents-velocity-2.11.2-sources.jar | Unknown | 15.75 KiB |
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:HYKaKraK:T92AKngL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HYKaKraK:T92AKngL"
}

