ViaEndlink v0.1.0

First tagged build of ViaEndlink — Minecraft: Java Edition players on an Endlink network.

Early work in progress, and marked a pre-release on purpose. The honest summary is that a Java player can get in and move around, not that the experience is good. Read the limits below before installing this anywhere real.

Install

Drop ViaEndlink.jar into Endlink's plugins/ folder and restart the proxy. That is the whole procedure — there is nothing to enable and nothing to add to the proxy's config. Remove the file and the proxy is Bedrock-only again, with nothing left behind.

The addon writes plugins/ViaEndlink/config.properties on first start: port, online mode, a name prefix to distinguish Java players in chat, and a resource pack URL.

Java clients from 1.7.2 to 26.2 can connect.

What works

Tested against a Minecraft 1.26.40 backend: joining, chat, the player list, terrain loading, backend switching, Mojang account verification, and the player's real IP reaching the backend.

onlineMode defaults to on: the session is checked against Mojang, and the player's name and UUID come from Mojang's answer rather than from whatever the client claimed. That is what stops both cracked clients and one player joining under another's name.

What does not

• Containers do not open — no chests, no crafting tables.
• Movement rubber-bands, because a Java client predicts motion and a Bedrock server does not agree.
• Custom addon items, blocks and entities have no Java equivalent and render as unknown.
• Block entities loaded from chunks are unreliable.
• Titles, subtitles, the action bar and name tags are drawn by Java as a single un-wrapped line, so multi-line Bedrock text is collapsed there. Signs do get their four lines.

Much of this is inherited from ViaBedrock, which does the actual translation and is upstream-described as early in development.

Requirements

• Endlink v0.1.0 or newer, on Java 21+
• Backends on the current Minecraft release. Older-version translation is deliberately unfinished — run the latest on both ends.

One side effect worth knowing

ViaBedrock speaks Bedrock 1.26.30 and nothing newer, so this addon registers a 1.26.30 → 1.26.40 upgrade edge in the proxy's protocol graph. A consequence is that installing it also lets real Bedrock 1.26.30 clients onto 1.26.40 backends. Those clients still authenticate normally through Xbox; it is a routing side effect, not an authentication one.

About this build

Built from a clean clone of this tag by CI on a Windows runner, and verified to contain all five local patches to the vendored ViaProxy and ViaBedrock sources before being published. ViaProxy.jar is carried inside ViaEndlink.jar, so an operator places exactly one file.

GPL-3.0 — required, because this embeds and links ViaProxy and ViaBedrock. Their sources, with the local patches applied, are vendored under bridge/ so anyone receiving this jar can rebuild it. Endlink itself remains Apache 2.0 and contains no GPL code.