Fixed bungeecord support that broke due to changes in bungeecord #18
Conversation
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
…e new [BungeeCord ChannelInitializer API](SpigotMC/BungeeCord#3776) - Updated the `bungeecord-proxy` dependency to 1.21.-R0.1-SNAPSHOT - Added a message when running an outdated bungeecord version (that doesn't support the new ChannelInitializer API) *Kept one and ported one funny comment* **Users are advised to upgrade their bungeecord proxies!**
… the deprecated v2
… the BungeeCord ChannelInitializer API
…t' into bungee-channelinitalizer-api-port
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.
Ported some changes from geyser/floodgate where they switched to the new BungeeCord ChannelInitializer API
bungeecord-proxydependency to 1.21.-R0.1-SNAPSHOTUsers are advised to upgrade their bungeecord proxies!