About

What it does

A map is an archive: the world in a LevelDB database, resource and behaviour packs, functions, scripts. Its text sits in a dozen different places — signs, books, item names, lore, NPC dialogue and buttons, commands, scoreboards, pack language files. Bedrockus walks through all of them, pulls the text out and shows it as one list, saying where each line came from.

It puts the translation back by the game's own rules. Whatever the game can read from a language file goes into .lang and gets a key; whatever it cannot read is written into the map as plain text. Commands like say and tell are rewritten into tellraw along the way, otherwise the translation would never show up in them.

The result is an ordinary .mcworld: it opens in the game as usual and follows the language the player has chosen.

How it works

• Upload. The file is taken apart on the server: LevelDB, NBT, pack archives. The result is a list of lines with coordinates, a category and an explanation of where each line will end up.
• Translation. Everything after that happens in your browser: filters, drafts, custom keys. You can translate on the page, or export CSV, XLIFF or .lang, work in your usual tool and load the file back.
• Build. The server assembles a new world: writes the language files, puts keys into signs and books, writes plain text where keys do not work, and hands you a finished .mcworld.

What it knows about the game

Some Bedrock rules are documented nowhere and were verified in the game itself — the whole translation layout rests on them.

Signs, books and NPC dialogue only pick up a translation through rawtext with a translate key. NPC buttons are the exception: they take a bare key and cut it at 16 characters, so button keys are kept short.

Item names and the world name understand no keys at all — text goes in there as it is. That is why the build dialog asks separately which language should be written straight into the world.

An en_US.lang file must always exist: the game falls back to it, and without it the key itself shows up where the translation should be.

What it does not do

• It does not store maps: an uploaded file lives on the server for at most an hour and is deleted together with its analysis.
• It has no accounts and asks for no registration.
• It does not translate for you: there is no machine translation inside — the text is yours or your translator's.
• It publishes nothing: the built world goes only to the person who uploaded the original file.

Legal

Bedrockus is an unofficial fan project. It is not affiliated with Mojang Studios or Microsoft, and is neither approved nor endorsed by them.

Minecraft is a trademark of Mojang Synergies AB. Rights to the game, its content, names and original texts belong to their respective owners.

Rights to the maps themselves belong to their authors. When you process someone else's map, it is on you to have the right to do so.

The icons in the interface are Tabler Icons (© Paweł Kuna), the GitLab SVG library and Material Symbols (© Google LLC); the language flags are flag-icons (© Panayiotis Lipiridis). The first three sets and the flags are used under the MIT licence, Material Symbols under Apache 2.0.