Vystorm-Core

One menu, one settings screen, one admin dashboard for every Vystorm plugin. Vystorm Core is the shared base all Vystorm plugins run on. On its own it adds little gameplay. What it gives your server is one consistent way to use them: a main menu, settings, an in-game config editor, an admin dashboard, translations, an update check and one database connection. Install it once, then add the plugins you want.

Features

Menus and settings

• One main menu. /vmenu lists every menu the installed plugins register, sorted into categories like Character, Economy or World. Players only see what they may open. Search, up to 20 favourites, the last eight menus opened, per-plugin tutorials and an optional "First steps" guide.
• One settings screen. /vsettings collects the personal options of all plugins (language, for example) and, for admins, the server options. Stage changes across several sections and apply them together after a preview, or save server values as a profile and load it later.
• Player menu. Sneak and right-click another player with an empty hand to see what you can do with them: the actions your Vystorm plugins offer (pay, invite, add as plot member, view stats ...) in one menu instead of commands with player names. It only opens when a plugin offers an action, otherwise the click works as before. Players can switch it off for themselves.
• Menus as real dialogs. Text input, confirmations and guides open as native Minecraft dialogs; inventories with real items stay inventories.

Administration

• Edit plugin configs in game. /vadmin config <plugin> opens a plugin's config.yml as a settings page: comments become descriptions, ranged numbers become sliders. Only changed keys are written, comments are kept, and a backup is made before the first save.
• Admin dashboard. /vadmin shows one module per plugin with its common admin actions as buttons. Actions that change something show the exact command and ask before running it. /vadmin permissions lists every permission node of Core and all Vystorm plugins.
• Update check. Every 6 hours Core asks SpigotMC which versions of your installed Vystorm plugins are current. Admins get one clickable line on join, and /vadmin updates lists installed and latest versions with download links. Hide a plugin or a single version with update-check.ignore. Only the public version endpoint is contacted.
• Diagnostics. See which plugin features are active, in a fallback mode or unavailable for a player; find out why a menu is hidden from someone; run dry-run data migrations.
• Translations. English and German ship with Core and with each plugin. Every player gets their Minecraft language by default and can pick another. Add a language by dropping in a file such as fr.yml; /vadmin language audit lists missing texts. When a plugin update adds new texts, they are written into your language files without touching your edits.

Shared services

• Plugin worlds and visits. Plugins can run their own worlds (dream worlds, arenas). Core saves the player's full inventory and state before a visit and gives it back on exit, disconnect, server stop or after a crash.
• Shared database. All Vystorm plugins can use one MySQL or MariaDB database through a single connection pool. Credentials live only in Core's config.
• Trade chat. /vtrade <message> reaches everyone with the receive permission (240-character cap, two-second cooldown).
• Smaller things. Clickable coordinates in chat (teleport for staff), a shared region register (/vregion), a shared budget of 4,096 particles per tick, and size-capped debug logs.
• Optional extras. A web panel (/web, off by default) and support for the optional Vystorm client mod. Players without the mod lose nothing.
• Developer API for menus, dialogs, settings, localization, the config editor, the player menu and plugin worlds.

Requirements

Put the jar into plugins/ and start the server. Core loads early (load: STARTUP). On first start Paper downloads the database libraries Core declares (HikariCP and the PostgreSQL driver), so the server needs internet access once. Never install two Core jars.

Commands & permissions

Further nodes: vystorm_core.config.<plugin> (edit one plugin's config), vystorm_core.chat.teleport (click-to-teleport coordinates), vystorm_core.worlds.bypass, vystorm_core.*. Commands and tab completion only show what the sender may use.

Configuration

plugins/vystorm_core/config.yml; new keys from later versions are read from the jar defaults.

• language.default: auto (each player's Minecraft language) or a fixed code.
• player-menu: enabled, require-sneak.
• update-check: enabled, interval-hours, notify-on-join, ignore.
• database.shared: the shared MySQL/MariaDB database, off by default.
• web: the web platform, off by default.

Good to know

• Anonymous statistics. Core (and only Core) sends anonymous bStats data about which Vystorm plugins run in which versions. Opt out with metrics: false or in plugins/bStats/config.yml.
• Review reminder. Once a Vystorm plugin has been installed for 7 days, the next admin who joins gets one short message with a review link. Each plugin asks only once; switch it off under review-reminder.

More from Vystorm

Vystorm Rails, VystormPortals, CustomTrees, XPVaultEconomy, BlockIntegrations, Vystorm Veins, Winter Is Coming, Vystorm Insomnia, Vystorm Gallery, Vystorm Paddock, Vystorm Snapshot, Vystorm Boards and Vystorm Estates, all free.

Free and open source (MIT).