Skip to content
Plugins

Broadcasterv1.1.2

Pythonby TheNINJALLOA wrapper plugin for MCXboxBroadcast to broadcast your server to Xbox Live.

pip install https://github.com/TheNINJALLO/endstone-broadcaster/releases/download/v1.1.2/endstone_broadcaster-1.1.2-py3-none-any.whl
Stars
3

PLUGINSBROADCASTER

# Install

C:\Users\you\bedrock_server\plugins\endstone_broadcaster-1.1.2-py3-none-any.whl

Use the animation for reference. Follow the plugin's README for exact steps.

# README

Overview

Endstone Broadcaster runs MCXboxBroadcast Standalone beside your Bedrock server so friends of the authenticated Xbox account can discover and join it. Release 1.1.2 targets Minecraft 26.60, MCXboxBroadcast reviewed builds 160–162, and its new NetherNet relay.

What it does

  • Provisions Java 21 when the Java on PATH or a cached runtime is too old.
  • Checks upstream at startup and every 12 hours, installing only reviewed builds 160–162. If latest is newer, it selects build 162 and logs that a wrapper update is needed. Downloads are checked before replacing the installed JAR, including SHA-256 when GitHub supplies a digest.
  • Supports schemas 7, 8 and 9, matching the installed JAR (160→7, 161→8, 162→9). Schema upgrades keep a copy at config.yml.pre-v<TARGET>.bak; existing backups are retained.
  • Queries the backend over NetherNet for live session details, with configured metadata as a fallback.
  • Handles older NetherNet status endpoints that reject the new broadcaster's query parameters with HTTP 404.
  • Passes authentication and status messages to the Endstone console.
  • Runs setup outside the server thread and restarts the helper if it exits. Healthy helpers keep running; upstream handles session rotation.

Compatibility

ComponentRequirement
Endstone API0.11 (endstone>=0.11.9,<0.12; current stable release: 0.11.14)
Minecraft / advertised Xbox session26.60, protocol 2225 in upstream build 160
BackendNetherNet HTTP signaling and support for the connecting client's game protocol
MCXboxBroadcast Standalone160–162; reviewed builds downloaded automatically
Java21+; portable Temurin 21 JRE installed if needed
Python3.11+; automatic tar extraction on Linux/macOS needs 3.11.8+
Plugin releasev1.1.2

Updating this wrapper updates the broadcaster, not the Endstone server binary or its game protocol. Endstone 0.11.14 is paired with BDS 1.26.52.3; use a server release or a protocol translator that accepts 26.60 clients as well as enabling NetherNet. Check the Endstone releases and your translator's compatibility before upgrading the server.

Install

Download endstone_broadcaster-1.1.2-py3-none-any.whl from the v1.1.2 release, or build it from this source. Back up the full plugin data folder and old wheel before installing.

  1. Stop Endstone and replace the old broadcaster wheel in plugins/ with the new wheel.
  2. Ensure the backend uses transport=nethernet in server.properties. Restart the backend after changing its transport.
  3. Start Endstone. Setup downloads need access to GitHub and, if necessary, Adoptium. Authentication and broadcasting need access to Microsoft/Xbox services.
  4. Follow the Microsoft sign-in URL and device code printed in the console. Existing cached accounts are reused.
  5. Add the authenticated broadcaster account as an Xbox friend, then join its Minecraft session.

The plugin data folder contains config.yml, endstone-broadcaster.jar, jar_version.txt, the optional jre-21/ runtime, and upstream's cache/. Keep this folder when upgrading to retain authentication and player history.

How NetherNet works in 26.60

Upstream build 160 removes the old transfer proxy. It relays Xbox session negotiation to the backend's HTTP signaling endpoint, gathers the client's ICE candidates, and sends the backend's answer back to the client. Game traffic then flows directly between the client and backend over WebRTC.

On older Endstone/BDS backends, a plain GET /v1/join can work while the new GET /v1/join?version=...&protocol=...&id=... probe returns 404. Version 1.1.1 starts a loopback HTTP adapter for the Java helper. If a probe with parameters returns 404, the adapter checks the plain endpoint and enables compatibility only when it returns valid NetherNet metadata for a protocol older than 26.60. Modern endpoints keep their query parameters, and HTTPS keeps its direct connection. SDP join requests and responses are forwarded unchanged; the official JAR is unchanged. No extra public port or config change is required.

This fixes the probe failure before game protocol translation. Endweave still needs to support the connecting client. A 26.5x backend can continue advertising its native protocol in its status response while Endweave translates the actual connection.

session.remote-address and session.remote-port identify the backend as reached by the helper. A helper running beside Endstone normally uses 127.0.0.1 and the server port. A specific server-ip binding is used when present; wildcard bindings are translated to loopback. Public IP lookup is no longer needed.

The backend must return a valid response from GET /v1/join and accept the negotiated WebRTC connection from external players. The helper needs TCP access to the signaling endpoint; players need access to the backend's configured UDP gameplay ports. Configure the backend's public ICE candidates and any NAT/port mappings in the backend or hosting panel. The wrapper does not configure these mappings.

For BDS, server-udp-ports belongs in server.properties. It is separate from the broadcaster's removed ice-port-range option. Merely seeing a session in the friends list does not verify external UDP reachability. See the Mojang NetherNet guide and Cloudburst/Geyser transport explanation.

Configuration

With build 162, the generated config.yml uses upstream schema 9. This is the core session section:

session:
  remote-address: 127.0.0.1
  remote-port: '19132'
  update-interval: 30
  query-server: true
  allow-ipv6: false
  config-fallback: true
  hide-old-sessions: true
  session-info:
    host-name: Endstone Server
    world-name: World
    game-mode: Survival
    players: 0
    max-players: 20
friend-sync:
  update-interval: 60
  auto-friend: true
  initial-invite: true
  expiry:
    enabled: true
    days: 15
    check: 1800
notifications:
  enabled: false
debug-mode: false
suppress-session-update-message: true
config-version: 9

During an upgrade from a legacy schema below 7:

  • session-info.ip and port are removed. The old public transfer destination is replaced with the local backend signaling endpoint.
  • query-server and config-fallback are enabled so the helper uses live backend metadata and tolerates a backend still starting.
  • auto-follow becomes auto-friend; auto-unfollow and ice-port-range are removed.
  • Notification settings, expiry rules, debug choices, and other custom values are preserved. YAML formatting and comments are normalized; the original file is backed up before migration.

For schema 7, 8 or 9 configs, explicit backend addresses, ports, query choices, and session rotation settings are retained. The host and world fallback names still follow server-name and level-name from server.properties. New configs also use its game mode and maximum player count as fallbacks. Stop Endstone before editing the file and start it again afterward.

If the helper runs in a different container/network namespace, set remote-address and remote-port to the address reachable from that container. Upstream also accepts auto for loopback and port 19132 in Standalone mode. Session and friend-sync update intervals must each be at least 20 seconds.

Malformed YAML, invalid endpoints/intervals, and future schema versions stop helper startup with an error instead of overwriting the file.

Schema 8 adds allow-ipv6: false without replacing explicit values. Schema 9 removes web-query-fallback, matching upstream. Migration from 7 or 8 does not reset endpoint or query preferences. An offline cached build 160/161 retains schema 7/8; a newer config is never downgraded to fit an older JAR. Upgrade download failure in that situation stops the helper with an actionable error instead of damaging config. Unknown installed builds are not silently downgraded or launched. JAR/config/version-marker replacement failures restore the prior matching files before attempting to restart the old helper.

Rollback: stop Endstone and restore the old wheel and the matching complete plugin data-folder backup (JAR, version marker, config, account cache), then start it. Do not pair the old schema-7-only wrapper with a schema-9 config. Cached JAR identity relies on jar_version.txt; this is not an independent inspection of the JAR's embedded version. Keep the marker and JAR together and do not relabel an old binary. If a rollback itself fails, recovery copies remain in broadcaster-update-* and startup/updates are blocked until the matching files are restored and that recovery directory is moved out of the data folder.

No live server or Xbox connection has been tested for this candidate; Linux Python 3.12 offline tests and wheel checks are documented in FIX-REPORT.md.

Commands and permissions

There are no Endstone commands or permissions. The helper starts and stops with the plugin. Authentication and errors appear in the server console.

Development and releases

python -m pip install pytest PyYAML ruff build
python -m ruff check src tests
python -m pytest -q
python -m build --wheel

CI runs the migration, Java selection, download validation, signaling compatibility, and process lifecycle tests on Windows and Linux with Python 3.11 and 3.14 before building the wheel. A v* tag publishes the wheel to its GitHub release. See the changelog for upgrade details.

Runtime credentials, account caches, logs, and server data must stay outside source control.

© 2023–2026 EndstoneMC

Not an official Minecraft product. Not approved by or associated with Mojang or Microsoft.