Skip to content

Conversation

@WhiteProject1
Copy link

Switched from ProtocolLib to PacketEvents for packet handling, updating dependencies and code accordingly. Added PacketEventsManager, removed ProtocolLibManager, and refactored TitleAPI to use PacketEvents for title, tab, and action bar messages. Updated pom.xml dependencies and plugin.yml to depend on PacketEvents instead of ProtocolLib.

Switched from ProtocolLib to PacketEvents for packet handling, updating dependencies and code accordingly. Added PacketEventsManager, removed ProtocolLibManager, and refactored TitleAPI to use PacketEvents for title, tab, and action bar messages. Updated pom.xml dependencies and plugin.yml to depend on PacketEvents instead of ProtocolLib.
@WhiteProject1
Copy link
Author

@Ajneb97

@Ajneb97
Copy link
Owner

Ajneb97 commented Jul 21, 2025

Nice! But I can't add these to the plugin, mainly because:

  1. The plugin has always worked with ProtocolLib, so removing support all of a sudden would not be ok. What would be better is to have a configurable option to decide whether to use ProtocolLib or PacketEvents.
  2. I don't know how to implement the API of PacketEvents, if something happens, a bug occurs, I have no idea how to fix it.
  3. Comments are not in english.

Introduces a PacketManager interface and implements ProtocolLibManager and PacketEventsManager for handling tab completion blocking. The plugin now supports both ProtocolLib and PacketEvents, with a new 'packet_library' config option to select the preferred library or auto-detect. Updates plugin.yml dependencies, configuration, and refactors EasyCommandBlocker to use the new abstraction.
@WhiteProject1
Copy link
Author

New changes not tested.

@WhiteProject1
Copy link
Author

@Ajneb97

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants