Repository navigation
docs: show the multiplexed port setup for bedrock dedicated server - #481
Merged
Merged
Conversation
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
NotGeri
marked this pull request as ready for review
November 19, 2026 09:40
Contributor
There was a problem hiding this comment.
All reported issues were addressed across 6 files
Tip: Get a Slack DM when cubic finishes reviewing your PRs. Connect Slack
View guided diff | Turn on auto-fix | Re-trigger cubic
This branch was successfully deployed
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.
Summary
Bedrock Dedicated Server now supports NetherNet multiplexing: several players share one UDP port. We confirmed it on 2026/11/18 by joining one server with three accounts through a single port, using
server-port=19132andserver-udp-ports=<public ip>:19132:19132. The public IP is required there because signaling can arrive through our TLS proxy rather than straight at the server.The NetherNet page still described the old setup: a TCP-only signaling port plus a range of UDP gameplay ports opened by the Max Players setting on the Startup tab, one per player slot, capped at 50. The panel no longer does any of that for BDS. The Max Players variable has been removed from the egg, so the player limit is set with
max-playersinserver.propertieslike any other Bedrock server, and the primary port carries both TCP signaling and UDP gameplay.Tracked in Linear as TEC-814.
Changes
server.propertiesexample and why the public IP is inserver-udp-portsmax-playersinserver.properties, and drop the 50 player cap noteTest plan
src/andembeds.ymlfor leftover references to the gameplay port range,server-udp-ports, Max Players and the removed section anchor and imagesNo screenshots: the change is page prose, and the preview deployment linked by the bot below shows the rendered pages.