Getting Started
EchoingDeaths drops onto any Spigot-family server in minutes. This page covers requirements, installation and the first commands worth running.
Requirements
| Requirement | Detail |
|---|---|
| Server software | Spigot, Paper or Purpur |
| Minecraft | 1.21+ (api-version: '1.21' in plugin.yml; built against the Spigot 1.21.8 API) |
| Java | 21 or newer (the plugin is compiled for Java 21) |
| Dependencies | None, no NMS, no reflection, no other plugins required |
Installation
- Download the latest jar from EchoingDeaths on Modrinth.
- Place it in your server's
/plugins/folder. - Restart the server. The plugin generates its default config on first boot.
- Edit
plugins/EchoingDeaths/config.ymlto taste, then run/echoingdeaths reload(or restart again).
Building from source instead? The project is plain Maven:
git clone https://github.com/PotenFYR-Studios/EchoingDeaths.git
cd EchoingDeaths
mvn clean package # requires JDK 21+; jar lands in target/First steps in game
With ops (or the echoingdeaths.admin permission), try:
/echoingdeaths info # version + author banner
/echoingdeaths reload # apply config edits without a restart
/echoingdeaths test LAVA # apply the Lava curse to yourselfStand next to a friend, have them jump off something tall, and watch the curse ripple out to everyone within the configured radius.
Troubleshooting
- No curses at all? Check
settings.enabledistrueand that your world isn't listed insettings.ignored-worlds. - Curses feel too weak/strong? Tune
settings.radiusand each curse'sduration-seconds/amplifier. - A player never gets cursed? They may hold
echoingdeaths.bypass, be in creative or spectator mode (seesettings.affect-creative/settings.affect-spectator), or be standing outside the radius. - Config edits not applying? Run
/echoingdeaths reload; effects are read from config on every death.
Still stuck? Ask in the support Discord or open an issue.