Commands
Every subcommand, its arguments, and the permission it needs.
One command, /wandworks, with /wands as an alias. Everything below works from the console as well as in game.
| Command | What it does | Permission |
|---|---|---|
/wandworks | Prints the subcommands you have access to | none |
/wandworks give <player> <wand> [uses] [amount] | Puts a wand in someone's inventory | wandworks.give |
/wandworks list | Lists every loaded wand id and its type | wandworks.admin |
/wandworks reload | Re-reads the config, wands, prices and language | wandworks.reload |
The bare /wandworks only lists the subcommands the sender can actually run, so a player with none sees just the header.
give
/wandworks give <player> <wand> [uses] [amount]| Argument | Required | Default |
|---|---|---|
player | yes | The player has to be online, and the name has to match exactly |
wand | yes | An id from wands.yml. /wandworks list shows them |
uses | no | The wand's own uses value |
amount | no | 1. Anything above 64 is capped at 64, anything below 1 is raised to 1 |
/wandworks give Steve seller
/wandworks give Steve seller 500
/wandworks give Steve builder 250 8A builder wand handed out this way starts on that player's last bag choice, or on the wand's bag-default if they have never switched it. See Bag mode.
The give is all or nothing. If the whole stack does not fit, the command says the inventory is full and the player gets none of it, so running it again once they have made room is safe.
Giving a wand to someone else tells them they received it. Giving one to yourself does not, since you already know.
list
/wandworks listPrints how many wands loaded, then one line per wand with its id and type. Fastest way to check a new entry in wands.yml actually parsed. A wand missing from this list failed to load, and the console will say why.
This one needs wandworks.admin rather than a node of its own.
reload
/wandworks reloadRe-reads config.yml, wands.yml, prices.yml and the language file, rebuilds the wand list and the price chain, and clears every cooldown.
Storage settings are read once at startup. A change to storage.type or the MySQL details needs a full restart. Everything else this picks up straight away.
If a file has a syntax error the reload fails, says so, and the plugin keeps running on the settings it already had. The console carries the reason.
Tab completion
Completion is filtered by permission, so a player only ever sees subcommands they can run.
| Position | Suggests |
|---|---|
/wandworks <tab> | The subcommands available to you |
give <tab> | Online player names |
give <player> <tab> | Every loaded wand id |
give <player> <wand> <tab> | 50, 100, 250, 500 as a starting point |
give <player> <wand> <uses> <tab> | 1, 8, 16, 64 |
The uses and amount suggestions are shortcuts, not limits. Type any number.