Commands
Base command: /mobs. The class-level @CommandPermission("mobs.command") on MobsCommand applies to every subcommand below — there is no separate per-subcommand permission node.
Command | Permission | Completion | Description |
|---|---|---|---|
|
|
| Spawn a mob blueprint at the sender's location. Player-only. |
|
| — | Reload the plugin configuration and blueprints. |
/mobs summon <blueprint>
Permission: mobs.command. Player-only — the handler takes a Player, not a CommandSender.
<blueprint> is resolved through MobBlueprintContextResolver, which pops the argument and looks it up with AstralMobs#blueprints().findById(id); an unknown id throws InvalidCommandArgument ("Mob blueprint '<id>' not found."). Tab completion (@mobBlueprints, backed by MobBlueprintCompletionHandler) lists the keys of AstralMobs#blueprints().all() — the ids of every loaded mob blueprint.
On success, MobService#summon spawns the resolved blueprint at the sender's current location (sender.getLocation()).
/mobs reload
Permission: mobs.command. No arguments; works from console or as a player.
Sends the reloading message, then calls AstralMobs#loadConfiguration(), which re-runs:
messages.ymlreloadconfig.ymlreloadBlueprintService#load()— re-scans every YAML file underblueprints/and rebuilds the id lookup used by/mobs summonand its tab completion
On success the sender gets reloaded, followed by a line showing the count of loaded blueprints. If loadConfiguration() throws, the exception is logged to console via AstralMobs#getSLF4JLogger() and the sender gets reload-failed instead.
Reload messages
The three reload messages are plain component values in messages.yml and can be edited freely:
Key | Default |
|---|---|
|
|
|
|
|
|
Permission summary
Node | Grants |
|---|---|
| Base node for |