Welcome to the Hangar Open Beta. Please report any issue you encounter on GitHub!
Shared base for Vystorm plugins: main menu, settings, in-game config editor, admin dashboard, update check.
- Fix: tab completion of a trailing greedy argument (
Arg.greedy) now asks its suggester for every word, not only the first one. - Fix: visited worlds' command allow-lists accept the active localized root aliases of an allowed Core command (
/aufwachenwhenwakeis allowed); the alias must belong to that command's plugin. - Fix:
adoptno longer offers a localized root alias that is already a plugin.yml alias of the command (it showed up as a collision with the plugin itself). - New: central command system (capability
commands, packagecommands, docs/API.md §24). Plugins declare a command tree (CommandSpec.command("rails").sub("dest", s -> s.arg(Arg.greedy("name").optional()).executes(...))) and register it withCoreCommands.register(plugin, lang, spec). Core parses and checks it (permissions, player-only, per-player cooldowns, async handlers, argument types: word, greedy, integer/decimal ranges, online player, player name, world, choice, enum, on/off, custom with own suggestions) and localizes everything a player sees from the plugin's language files: subcommand names (commands.<cmd>.sub.<id>.name,.aliases), keyword values (on/an/开, shared in Core'scommand.values.*), tab completion, usage lines, generated clickable and paged help (/<cmd> help,hilfe,帮助,?) and the error messages (no permission, player only, unknown subcommand with a clickable "did you mean", missing/bad argument with the usage line, cooldown). Every installed language's names are accepted for everyone (/rails ziel=/rails dest=/rails 目的地); completion and help use the player's own language and follow/languageat once (PlayerLanguageChangeEvent). Registered through Paper's Brigadier lifecycle API while plugins start, otherwise through the Bukkit command map; works from the console. - New: localized root aliases. Command labels are global on a server, so the English label and the fixed aliases always exist and the aliases from
commands.<cmd>.aliases(e.g./schienen,/铁轨for/rails) are registered server-wide as the admin chooses:config.ymlcommands.localized-aliases: all(default; every installed language),default(only the server language) ornone; single aliases can be switched off (commands.disabled-aliases). They are applied on the first server tick, after every plugin's own commands exist, and never take a label another command has (skipped and shown as collision). - New:
/vhelp [plugin] [page](/vhilfe,/befehle,/v帮助,/vcommands): all commands of all Vystorm plugins the player may use, grouped by plugin, in the player's language, clickable (opens the help or types the command). Plugins that have not migrated are listed from plugin.yml; they can localize their line withcommands.<name>.description. - New:
/vadmin commands [page]: every registered tree with mount (paper, bukkit, adapter), fixed aliases, localized aliases with state and the owner of a colliding label, clickable on/off per alias, subcommand name conflicts per language and the plugin.yml commands not migrated yet;/vadmin commands mode all|default|noneand/vadmin commands alias <alias> on|offwriteconfig.ymland apply at once. - API:
CoreCommands.adopt(plugin, lang, declaration)wraps an existing plugin.yml command for step-by-step migration: the old executor gets localized names translated to the English ids, Core adds help, merged localized completion, root aliases and the/vhelpentry.CoreCommands.find(label)resolves localized aliases (for mute filters and similar),CommandRegistration.execute/suggest/help/usagerun a tree directly,CommandTesting.detached(...)tests a tree without a server. New permissionvystorm_core.commands.bypass-cooldown(op). German migration guide with an estimate per plugin:docs/COMMANDS-MIGRATION-de.md. - New: Simplified Chinese (
zh_cn) as a first-class language. Core ships a completelang/zh_cn.yml(all keys ofen.yml, Minecraft's official zh_cn terms such as 物品, 方块, 世界, 菜单, 设置; every{placeholder}, MiniMessage tag and&code unchanged, checked by tests). Clients with the Minecraft language 简体中文 get it automatically; 繁體中文 clients (zh_tw,zh_hk,zh_mo) too while no own file exists. Plugins addsrc/main/resources/lang/zh_cn.ymlthe same way; it is copied toplugins/<Plugin>/lang/zh_cn.yml. The web panel (/core/i18n, language switch) serveszh_cnas well;Accept-Language: zh-CN,zh-TWandzhresolve to it. - New:
/language(aliases/lang,/sprache,/语言; permissionvystorm_core.language, everyone). Without arguments a chest menu with "Automatic (client language)" and one flag-like banner per language: its own name, code and how much of it is translated over all plugins; the current choice glows./language <code|auto>sets it directly (alsozh-CN,de_at→de, or the language's own name, with tab completion),/language listlists. Admins:/language <player> [code|auto]shows or sets another player's language, also from the console (vystorm_core.language.others, op, part ofvystorm_core.admin). The choice is the same stored value as/vsettings→ Language (which stays), so both are always in sync; the/vsettingsoption list now follows the available languages and refreshes after plugins load and on reload. - Offered languages: the union of the language files of all registered bundles, shown when Core has the language or its coverage over all plugins reaches
language.min-coverage(default 50 %), so a plugin-only file with a handful of texts does not appear as a language. - New: fallback chain. Missing texts fall back key by key along
zh_tw → zh_cn → en,de_at → de → en,de_ch → de → en(code, configured step, language part, English); also used to pick a file for a client locale. Built-in stepszh_hk/zh_mo→zh_tw,zh_tw/zh_sg/zh→zh_cn,pt/pt_pt→pt_br,nn/nb→no;language.fallbackin Core'sconfig.ymladds or removes steps (fr_ca: fr,zh_tw: none). - New:
language.server(defaulten): language of the console and of players whose language has no file (instead of always English), andlanguage.force(defaultfalse): everyone gets the server language,/languageexplains that the server uses one language (choices are kept for later). /vadmin language audit [plugin|*] [lang]now reports per plugin and language the coverage, missing keys, untranslated keys (identical to English) and placeholder mismatches with counts; filtered by plugin or language it lists the keys. Every line has a clickable [export].- New translator workflow:
/vadmin language export <plugin> <lang> [yml|csv]writes every key with the English source, the current translation and a status toplugins/vystorm_core/translations/<plugin>.<lang>.yml(CSV with BOM for spreadsheets);/vadmin language import <file> [plugin] [lang]merges a reviewed file into the plugin's override folderplugins/<Plugin>/lang/<lang>.yml(never the jar), keeps the old file as<lang>.yml.bak-<date-time>, skips unknown keys and texts whose placeholders differ from the source, and reloads the bundle. Admin-edited files keep surviving plugin updates: only new keys are added from the jar. /vadmin language reloadreloads all bundles and thelanguage.*settings without a restart, refreshes/vsettingsand tells plugins (event below). Saving Core's config in the config editor does the same.- Width of Chinese text: new
lang.TextWidth(display columns with full-width characters counting 2, approximate default-font pixels, CJK-aware wrapping that never starts a line with,。!?and keeps“(with the following text, centring, padding, truncating, colour codes carried over) andLang.wrappedLines(...)for item lore; the language menu uses it. Command hints such as<plugin>after a full-width colon (:/vadmin …) are no longer reported as unfilled tags by the audit. - API:
Localization.fallbackChain,fallbacks,coverage,selectableLanguages,serverLanguage,forced,minCoverage,configure(ConfigurationSection);Lang.coverage,counts,keys,translation,bundledTranslation,folder,audit(lang),wrappedLines,Audit.untranslated()/coverage();PlayerLanguageChangeEvent(after/language,/vsettings, admin change, a new Minecraft language while on "Automatic", reload; plugins redraw boards and menus there) andCoreLanguage.setChoice(player, code, cause); capabilitylanguage-selection. See docs/API.md §4.3. - Fixed: YAML documents loaded through Core (data entries
core.data(),AtomicFiles.readYaml, the config editor) kept every SnakeYAML node of the file in memory for as long as the document lived. Bukkit'sYamlConfigurationbuilds its values node by node, and SnakeYAML's per-document node cache is never cleared on that path, so each loaded entry held twoScalarNodes with theirMarks and comment lists (about 500 bytes per entry), and every reload of the same object added another set. Core keeps its data entries for the whole server run: on a live server a plugin with 270,000 chunks in such entries held about 900 MB this way (heap summary 30.10.2026: 7.2 millionMark, 3.6 millionScalarNode). Core now empties that cache right after loading (YamlNodes.release, what SnakeYAML itself does at the end of a document). Nothing that was loaded changes; on a Bukkit/SnakeYAML without this cache it does nothing. Measured with the old WorldForge and 270,000 chunks: live heap 2.45 GB → 1.51 GB. Plugins that keep their ownYamlConfigurationobjects can callYamlNodes.release(config)after loading. - Minecraft 26.3: client biomes (
ClientBiomes.snow,project; Winter's packet snow, Portals' biome preview) now also run on Paper/Purpur 26.3.ClientBiomes.supported()accepted only 26.2, so on 26.3 Winter fell back to particles. 26.3 keeps the 26.2 biome packet format (checked against the 26.3 server jars: sameChunkBiomeDataconstructors, ChunkPos + byte array codec, unchanged palette encoding) and was tested with a protocol bot on Paper 26.3 #231 and Purpur 26.3 #2655. Other versions are still reported as unsupported. - Tested on Paper 26.3 #231 and Purpur 26.3 #2655: client displays (
ClientDisplays) pass their packet probe unchanged, seeCOMPATIBILITY.md.
Platforms
Paper
1.21.8–26.3
Dependencies
Paper
- Vault Optional