Commands & Permissions

Everything the plugin registers, straight from plugin.yml and the command executor.

Commands

The base command is /echoingdeaths, with /ed registered as an alias. With no arguments it prints the help menu.

Command	Permission	Description
`/echoingdeaths` · `/ed`	`echoingdeaths.admin`	Base command; prints the help menu.
`/echoingdeaths reload`	`echoingdeaths.reload`	Reloads `config.yml` from disk and confirms in chat.
`/echoingdeaths info`	`echoingdeaths.admin`	Shows plugin version, author and a short description.
`/echoingdeaths test <cause>`	`echoingdeaths.admin`	Players only. Applies the curse configured for `<cause>` (case-insensitive, uppercased) to yourself, including the configured messages, a safe way to preview any curse. Unknown causes resolve to the fallback curse.

<cause> is a Bukkit DamageCause enum name such as FALL, LAVA or SONIC_BOOM, the same keys used under effects in config.yml.

All three nodes default to server operators.

Permission	Default	Description
`echoingdeaths.admin`	`op`	Gate for the whole `/echoingdeaths` command (declared on the command in plugin.yml).
`echoingdeaths.reload`	`op`	Required for the `reload` subcommand, checked again at execution time.
`echoingdeaths.bypass`	`op`	Holders are never cursed by nearby deaths, checked per player when a curse spreads.

Base gate: plugin.yml attaches echoingdeaths.admin to the command itself, so players without it can't invoke /echoingdeaths (or /ed) at all.
Reload double-check: reload re-checks echoingdeaths.reload at execution time, so you can grant reload without granting info/test access only if you also negate the admin node; by default ops hold both.
Bypass: echoingdeaths.bypass is checked for each nearby player during a death, not at command time. It's the node to give to staff you don't want cursed.