Commands and Permissions

The command in use is /simpletreasure with /treasure as shortcut.

Command	Function	Permission
/treasure reload	Reload the default configuration file, i.e. "config.yml".	simpletreasure.reload
/treasure reload <file name>	Reload the given file as configuration, this will be used for the hide command if nno file is given.	simpletreasure.reload
/treasure info	Show which file is used and number of treasure defs.	simpletreasure.info
/treasure hide <tries> <radius>	Attempt <tries> often to hide a treasure within radius blocks distance of the player. (no circular)	simpletreasure.hide
/treasure hide <file name> <tries> <radius>	Use a specific configuration file for this hiding action. Will not replace the one set by reload.	simpletreasure.hide
/treasure hide <tries> <radius> <world> <x> <z>	Attempt <tries> often to hide a treasure within radius blocks distance of the coordinates. (no circular)	simpletreasure.hide
/treasure hide <file name> <tries> <radius> <world> <x> <z>	Use a specific configuration file for this hiding action. Will not replace the one set by reload.	simpletreasure.hide
/simpletreasure abort	Abort all running hiding tasks. Can be useful if you mistyped something.	simpletreasure.abort

Notes:

Reloading a specified file might allow players to use malicious path names, so be sure not to give everybody the permission for this.
The example from examples/default.yml will be copied to config.yml if config.yml is not present.
Some example files will be copied to the folder examples if not present there. If you update to a new version, delete the old files to have the new ones copied to examples.
If you want to use and alter example files, it is recommended to copy them out of the examples folder to avoid mixing them up.
To regenerate deleted example files use /reload.
You can specify a sub folder to load a treasure, i.e. "/treasure reload examples/epic.yml" or "/treasure hide examples/chainmail.yml 100 20"

Comments