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.
- New: server news board. Admins write short posts in game (
/vmenu news→ Write, a dialog with title and text) or with/vadmin news post <title> | <text>(also from the console);/vadmin news [list|write|delete <number>]manage them. Players who have not read a post get one clickable chat line when they join, online players get a line as soon as a post is published, and the main menu shows "News (2 new)". Clicking opens all posts in a dialog, writers also see Write and Delete buttons there. Players can switch the join line off in/vsettings→ News. Posts are plain text (no colour codes), stored innews.yml, hidden and removed afternews.max-age-days(30) and capped atnews.max-posts(20). Settings undernews(enabled,notify-on-join,announce-new-posts,max-age-days,max-posts); permissionsvystorm_core.news(everyone) andvystorm_core.news.write(op, included invystorm_core.admin). - API:
news.News.post(plugin, title, text),posts(),unread(player),open(player), capabilitynews, so plugins can announce events on the board. - New: change history of the config editor with undo. Every value saved through
/vadmin config(sections, drafts and settings profiles) is recorded inconfig-history.ymlwith admin, time, plugin, file and value before and after (secrets never)./vadmin config history [plugin] [page]lists the changes newest first, each with a clickable [undo]; the config menu has a "Change history" button. Undo puts the old values back with the usual backup and reload and is recorded itself. If a value was changed again since then, Core lists it and only overwrites it with "undo anyway" (/vadmin config undo <number> force). Only plugins you may configure (vystorm_core.config.<plugin>) are shown. Settings underconfig-history(enabled,max-entries= 200). - API:
ConfigEditor.history(viewer, plugin, page)andConfigEditor.undo(viewer, id, force), capabilityconfig-history. - Update check fallback list now also knows Vystorm Rails (SpigotMC 140076).
- Loot now uses Vystorm Core weighted loot tables everywhere: one model of tables → categories → rolls (see
docs/LOOT.md). - New: basic vanilla loot lists in
loot-vanilla.yml, standard Minecraft items only: tiersvystorm_core:vanilla/common,uncommon,rare,epic,legendaryand themesfood,ores_ingots,tools_weapons(with enchanted variants),armor,building,redstone,magic(books, potions, XP bottles),nether,end,ocean,treasure(discs, trims, sherds),fishing, plus mixesvystorm_core:default/<situation>. - New: loot categories in
loot-categories.yml(category:dungeon_chest,boss_chest,mineshaft_cart,treasure_vault,cave_loot_room,sky_temple,sky_wreck,fishing,expedition,mob_drop_common/_elite/_boss,quest_reward,contract_reward,arena_reward,event_reward,farm_rare_find,gathering_find,shrine,meteor). Vystorm plugins roll their category with their own list; by default nothing changes for them, and admins can retune e.g. all boss chests of all plugins in one place. - Loot tables can be
mode: each(every entry checked with its ownchance, for classic drop lists). Loot entries can now reference other tables (table: <id>,table: self), enchant items (enchant-levels,treasure-enchants), set apotiontype, have conditions (min-y,max-y,environments,biomes,min-difficulty,max-difficulty) and be afallback. Rarity tiers: common 0-3999, uncommon 4000-6999, rare 7000-8999, epic 9000-9799, legendary 9800-10000. - New admin commands:
/vadmin loot list [tables|categories],show <id>,roll <id> [luck= tier= min-tier= pity= rolls= seed= source= self= difficulty= y=](preview, nothing is given) andsimulate <id> <n> [options](distribution per tier and item),give <id> [player] [options](gives one roll for testing),reload. - API:
loot.LootRoll(luck, tier/weight filters, pity, unique, exclude, seed, context; pureroll()for async populators,generate()),LootResultwith hit metadata,LootTier,RollContext,LootLuck(player luck = Luck attribute + plugin sources),LootTables.choose/exists/owner,LootTableConfig.load(plugin, files...),LootTable.ranksFor(...)for converting old relative weights; capabilityloot-rolls. Plain tables roll exactly as before (same random sequence).
Fixed:
- Config history: undoing an undo marks the original change as active again (no more "undone by #N" and the undo button is back), since its values apply again.
- An unreadable
news.ymlorconfig-history.yml(for example after a hand edit with a YAML error) was loaded as empty and overwritten by the next post or config change, so all posts or the whole history were lost. The file is now moved aside as<name>.broken-<date-time>, the console explains how to restore it, and nothing is saved over it until the next restart. The same forreviews.yml(review reminder state). - Generating the web gateway secret no longer rewrites an unreadable Core
config.ymlwith only the secret in it, and writes the file atomically. - XML data entries are now saved atomically (temp file + move) like YAML entries.
- API:
AtomicFiles.moveAside(path)moves an unreadable data file aside as<name>.broken-<date-time>. menu.ymlandresource-pack.ymlwere written directly (an interrupted write could empty them), and an unreadable one (for example after a hand edit with a YAML error) was silently reset to the defaults, losing the pause-menu or resource pack settings. They are now written atomically; an unreadable file is moved aside as<name>.broken-<date-time>, the console says so, the defaults are used in memory and the file is not written again until the next restart.- API:
AtomicFiles.readYaml(path, logger)loads a YAML file and moves it aside when it is unreadable (returnsnullthen).
Platforms
Paper
1.21.8–26.3
Dependencies
Paper
- Vault Optional