Welcome to the Hangar Open Beta. Please report any issue you encounter on GitHub!
Avatar for Vystorm

Shared base for Vystorm plugins: main menu, settings, in-game config editor, admin dashboard, update check.

Report Vystorm-Core?

R

0.65.0-Vystorm-Core-26.2

  • Placeholder manager. Core now keeps the values of all Vystorm plugins in one place. A plugin registers its values once (balance, level, region, votes ...), and you can show them as %vystorm_<plugin>_<value>% in every plugin that uses PlaceholderAPI (scoreboards, tab lists, holograms, chat formats) and as {plugin:value} in the texts of Vystorm plugins. /vadmin placeholders lists every value with a description; /vadmin placeholders test <text> shows a text the way a player sees it.
  • Core's own values: player name, display name, UUID, world, coordinates, players online and the limit, server time and date (with your own pattern), the clock of a world, language, TPS and tick time, ping, experience, health, food, game mode, the region the player stands in with its flags, the party, the Vault balance and the character level. Examples: %vystorm_core_online% and {core:time:HH:mm}. The full list is in docs/API.md.
  • PlaceholderAPI bridge. If PlaceholderAPI is installed, Core registers the expansion vystorm by itself (nothing to download), and texts resolved through Core also show placeholders of other plugins such as %player_name%. The start order of PlaceholderAPI and Core does not matter. Without PlaceholderAPI nothing changes. Switches: placeholders.placeholderapi.provide, consume and consume-async in Core's config.yml. The bridge was tested against our own stub of PlaceholderAPI only; please report problems you see with the real plugin.
  • Placeholders in language files are possible with placeholders.in-messages: true in Core's config.yml. It is off by default, so every existing text stays as it is.
  • What a placeholder inserts is shown as plain text: a player name or chat line with <red>, a click tag or another placeholder is never interpreted.
  • Scoreboard and chat plugins often ask for placeholders from a background thread. Values Core can answer there safely (names, positions, counts, clock, TPS, regions) work as usual; values that need the server thread (party, economy balance, character level, language) stay as written in such a plugin. /vadmin placeholders <namespace> marks them.
  • Menus from files. Design a screen menu in the web editor at https://vystorm.net/werkzeuge/menue-editor, save the file and put it into plugins/vystorm_core/menus/. Core shows it as a screen menu, as a grid of tiles like a chest, or as a free panel, with labels, buttons, item icons, pages and a footer description. It opens with /vmenu <id>, with its own command if the file names one, and from a tile in the main menu. A click can run commands as the player or the console, send a message, open another menu, go back or close, each with a permission and a cooldown. /vadmin menus lists the files and says what is wrong with one that was skipped; /vadmin menus reload reads the folder again. A broken file never stops the others. Give console commands a permission or a cooldown (Core warns when a file has neither). Switch: menus.enabled. Guide: docs/MENUS.md.
  • Screen fixes. A click on a screen that closed it or opened another one could reach the block behind it (in creative mode the block broke, a right click used a lever, door or chest). The new screen now catches clicks from its first tick, and for half a second after such a click block breaking, use and hits are cancelled for that player.
  • Screen fixes. A chest menu could lose its click protection when Core showed it as a real chest instead of a screen (screens switched off, a screen that could not open, the "Chest" button), so items could be taken out. Such a menu now stays protected however it is shown.
  • Screen fixes. One left click on a switch in /vadmin features could flip it twice. /screen classic on|off, /vadmin trace and the network commands answered with a text key instead of a sentence; the missing texts are added to your language files at the next start.
  • Command visibility. Tab completion and /vhelp follow feature switches at once, without a restart. For plugin authors: CommandSpec.Builder.visibleWhen(...) and api.command().refresh(); registering the same label again after startup on Paper now replaces the tree inside the existing registration.
  • Performance. The event order no longer builds a text label for every handler call (about 30 down to about 5 nanoseconds per handler). Core no longer reads every NBT tag on block, damage, interact and item events while no NBT action is registered (about 1.3 to 1.9 microseconds saved per event). A click in a chest, barrel, furnace or hopper no longer copies the whole block to check for Core's own menus (Core's share of a click went from about 125 to about 8 microseconds).
  • Switches for Core's own features, all on by default and listed in /vadmin features vystorm_core: trade-chat.enabled, clickable-coordinates.enabled, tutorials.enabled, setup.enabled, diagnostics.enabled, loot.enabled, plugin-worlds.enabled, region-register.enabled and menus.enabled. Older keys now on the feature screen as well: menu.sneak-click-shortcut, messages.show-source, the screens.* switches, metrics, update-check.enabled and review-reminder.enabled; the last three apply at once now. A switched-off feature answers "This feature is switched off on this server." in seven languages.
  • For plugin authors: api.placeholders().register(plugin, "namespace") with value, player, global, relational and resolver; PlaceholderTesting.detached() for tests; api.gui().fileMenus() for menus from files. See docs/API.md.

Information

Published
November 18, 2026
Author
2Downloads

Platforms

Paper
Paper
1.20.6–26.3

Dependencies

PaperPaper

Dependencies: Paper

Plugins and libraries a server needs for this version to run.

No dependencies

Add anything a server has to install alongside this version.