BrasaLink

Context

Servers that welcome both Java and Bedrock players, through Geyser, run into the same wall: an item with its own texture shows up correctly on Java and without the texture on Bedrock. Fixing this by hand, item by item, is a job that never ends.

Challenge

Converting Java’s modern item definitions into a package Bedrock understands, without breaking the server when an item isn’t compatible — and being able to roll back if an update goes wrong.

Solution

• Diagnostics before publishing. BrasaLink reads the item definitions, resolves legacy models and texture references, and blocks the entire publication if a single item is incompatible, saying why.
• Immutable releases, with the hash of each file and an atomic pointer swap. The previous release is preserved, and a rollback checks every file before activating it.
• Three pieces working together: the plugin on Paper, the extension on Geyser, and a command-line tool to diagnose, build, verify, and roll back outside the game.

Result

It’s in free beta for administrators. Updating and rolling back a texture were confirmed on both Java and Bedrock clients, in the reference set of Paper 1.21.4, Geyser 2.11.2, and ViaVersion 5.11.0. The beta’s scope is stated plainly: static 2D items; blocks, entities, and armor are for later.