feat!: replace ProtocolLib integration with PacketEvents#2982
Merged
Conversation
Xephi
force-pushed
the
feat/packetevents
branch
4 times, most recently
from
ac090b3 to
dcc7554
Compare
|
When it can be merged to the main |
Contributor
Author
When it would be tested :D |
PacketEvents becomes the single packet interception backend so inventory protection and tab-complete blocking follow the new platform adapter lifecycle across all deliverables. BREAKING CHANGE: features that previously depended on ProtocolLib now require PacketEvents, and plugin manifests, docs, and test fixtures have been updated to reflect the new optional dependency
Xephi
force-pushed
the
feat/packetevents
branch
from
dcc7554 to
04f5b39
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PacketEvents becomes the single packet interception backend so inventory
protection and tab-complete blocking follow the new platform adapter
lifecycle across all deliverables.
BREAKING CHANGE: features that previously depended on ProtocolLib now
require PacketEvents, and plugin manifests, docs, and test fixtures have
been updated to reflect the new optional dependency