docs: show the multiplexed port setup for bedrock dedicated server
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=19132 and server-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-players in server.properties like any other Bedrock server, and the primary port carries both TCP signaling and UDP gameplay.
Tracked in Linear as TEC-814.
Changes
- Rewrite the Bedrock Dedicated Server section of the NetherNet page for one port with TCP and UDP, with the matching
server.propertiesexample and why the public IP is inserver-udp-ports - Point the player limit at
max-playersinserver.properties, and drop the 50 player cap note - Update the technical overview to say both BDS and GeyserMC multiplex
- Remove "Ports Opened by a Startup Setting" from the Ports & Connections guide, since no server type opens ports that way any more
- Delete the screenshots that showed the old port range, the Max Players setting, and the signaling port with UDP closed
Test plan
- Searched the docs,
src/andembeds.ymlfor leftover references to the gameplay port range,server-udp-ports, Max Players and the removed section anchor and images - Preview deployment builds and the NetherNet and Ports & Connections pages render without broken images or links
No screenshots: the change is page prose, and the preview deployment linked by the bot below shows the rendered pages.