fix(bungee): start the proxy bridge without PacketEvents installed - #3149
Merged
Xephi merged 1 commit intoSep 22, 2026
Merged
Conversation
AuthMeBungee failed to load on proxies without PacketEvents: the bridge constructor instantiated the PacketEvents-backed premium verification manager, so the JVM resolved PacketEvents classes while linking that class and threw NoClassDefFoundError. The availability check inside the manager therefore never ran. The manager is now created through a factory that only loads the PacketEvents-backed implementation when the packetevents plugin is present and falls back to a no-op implementation otherwise, mirroring the lazy pattern already used by the Spigot platform adapter. A failed onEnable no longer causes a NullPointerException in onDisable either.
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.
AuthMeBungee failed to load on proxies without PacketEvents: the bridge constructor instantiated the PacketEvents-backed premium verification manager, so the JVM resolved PacketEvents classes while linking that class and threw NoClassDefFoundError. The availability check inside the manager therefore never ran.
The manager is now created through a factory that only loads the PacketEvents-backed implementation when the packetevents plugin is present and falls back to a no-op implementation otherwise, mirroring the lazy pattern already used by the Spigot platform adapter. A failed onEnable no longer causes a NullPointerException in onDisable either.
Closes #3148