Server I18n API

Blueprints An in-game node editor for Minecraft 1. 21. 11. Place nodes, wire them, declare typed variables — and the graph runs server-side on real world events. Not related to Blueprint by Team Abnormals, nor to the mod called Blueprints — the names collide, the projects do not. This one is blueprints-mod . Its mod id and namespace stay blueprint , because renaming them would break every graph already written. Declare a command, get a command A graph that declares home gets a real /home — no prefix, with tab-completion, like any other command on the server. Names already taken are refused rather than silently stolen: /kill stays vanilla's. on blueprint:event/command(player, name, arg) @with(name: "home") { blueprint:flow/branch(condition: blueprint:var/get(var: "defini")) { true: { blueprint:entity/teleport(entity: $player, pos: blueprint:var/get(var: "point")) } false: { blueprint:player/send_message(player: $player, text: "No home set — use /sethome") } } } Graphs are text, and text is graphs That snippet is not pseudo-code. It is BScript , the exact text every graph compiles to — and every BScript parses back into the same graph. Not an export: a round trip , guarded by tests on every build, including tests that re-read the examples shipped with the mod. That is what makes a graph reviewable in a pull request, diffable, and pasteable into a chat window. Copy in the editor, paste in Discord, paste back into the editor. What it costs a server A node editor invites the assumption of a slow interpreter. These are measurements, taken by benchmarks committed to the repository that fail the build if they drift. Active graphs on server_tick Scheduling time per tick Share of the 50 ms budget 50 ~0. 25 ms 0. 5 % 200 ~0. 6 ms 1. 2 % Every graph runs on a fuel budget . A runaway loop is cut and reported, not left to take the server down. A graph that faults repeatedly disables itself. And you can check it yourself, in-game, in three commands: /blueprint bench /bench /blueprint profile blueprint:bench The bench is a real graph — three nested loops — that you can open, read and edit in the editor. Nothing is hidden behind a benchmark harness you cannot see. What is in the box A full editor — palette, typed wiring, literals on nodes, variables and scopes, undo/redo, copy-paste as BScript, clickable diagnostics, script view, comments, minimap, a reloadable JSON theme, keyboard navigation. 239 node types — screens (34), maths (20), world (20), player (19), strings (12), flow (12), entities (12), vectors (11), logic (10), lists, maps, text, items, scoreboards — including 26 events . Typed variables that persist — numbers, text, booleans, plus vectors, block positions and directions, in five scopes from per-execution to world-wide. A player's home point survives a restart. A screen designer — 12 widget kinds (labels, buttons, lists, dropdowns, sliders, toggles, inputs, progress bars, item slots, images, entity previews, panels), with bindings : a label can follow a v