Commands

/collections

Opens the collections menu for the sender. The menu is computed with a single context entry — collections → an ItemProvider of every loaded blueprint — so layouts can iterate it with provider: "%parameters_collections%".

The menu YAML lives at plugins/AstralCollections/menus/collections.yml and uses the standard AstralCore menu system. Edit it freely; the plugin only supplies the data.

If the menu fails to compute, the player receives the error-occurred message and a stack trace is logged to the server console.

/collections reset <player>

Permission: collections.reset

Clears the target player's discovered entries and completed-collection set. Useful for testing or seasonal resets.

Tab-completion is wired up to online players (@players).

Players who have never opened the plugin (no AstralSync data yet) receive the error-occurred message — there is nothing to reset.

/collections reload

Permission: collections.reload

Reloads in this order:

1. loadConfiguration() — re-reads messages.yml and reloads the menu container.

2. BlueprintService.load() — re-scans every YAML in blueprints/ and rebuilds the lookup index.

The sender receives the reloading message immediately and either reloaded-successfully or reload-failed once the work is done. On failure a stack trace is written to the console.

Reload is non-destructive: players keep their progress, even if a blueprint is removed (its entries simply stop matching going forward).

Permission summary