Fix SOCKS5 UDP proxies not working with Bedrock Edition#947
Merged
AlexProgrammerDE merged 1 commit intoAlexProgrammerDE:mainfrom Feb 24, 2026
Merged
Fix SOCKS5 UDP proxies not working with Bedrock Edition#947AlexProgrammerDE merged 1 commit intoAlexProgrammerDE:mainfrom
AlexProgrammerDE merged 1 commit intoAlexProgrammerDE:mainfrom
Conversation
AlexProgrammerDE
approved these changes
Feb 24, 2026
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
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.
This pull request refactors how proxies are injected into Netty channels, specifically improving support for Bedrock connections and clarifying the API for adding proxies. The main change is that the
addProxymethod now takes aChannelinstead of aChannelPipeline, allowing for more precise handling of Bedrock (RakNet) channels and better error reporting.Netty proxy injection improvements:
addProxymethod inNettyHelperto accept aChannelinstead of aChannelPipeline, and updated all usages accordingly. This enables the method to access both the pipeline and channel-specific features. [1] [2]RakClientChanneland injects the handler into the RakNet pipeline. If the channel is not aRakClientChannel, an informative exception is thrown.NettyHelper.javato support the new channel type checks and handler injection.