Installation

The process is identical for every plugin we publish.

Download the jar

Grab the latest build from the release page of the plugin you want. Always download the file named PluginName-x.y.z.jar — never a -sources or -javadoc artifact.

Drop it into `plugins/`

Stop the server first. Hot-swapping jars with /reload corrupts config state and is not supported.

- - AquaCore-2.0.0.jar
  - AquaTags-1.3.1.jar
  - PlaceholderAPI.jar
- server.jar

Start the server

On first boot the plugin creates its own folder and writes the default files.

- - config.yml
  - messages.yml
  - modules.yml

Verify it loaded


[INFO] [AquaCore] Loading AquaCore v2.0.0
[INFO] [AquaCore] Detected Paper 1.21.4 (Folia: false)
[INFO] [AquaCore] Hooked into PlaceholderAPI
[INFO] [AquaCore] Loaded 3 templates, 12 messages
[INFO] [AquaCore] Enabled in 84ms

Configure and reload

Edit the YAML files, then apply them without a restart:


/aqua reload

Updating

Minor update (1.4.0 → 1.4.1)

Stop the server, replace the jar, start it again. New config keys are appended automatically and your existing values are preserved.

Never use /reload or /reload confirm to update a plugin. Bukkit’s reload leaks the old classloader, duplicates listeners and produces bug reports we cannot reproduce.

Common install problems

Symptom	Cause	Fix
`Unsupported class file major version 61`	Server running Java 8/11	Install Java 17+
`Plugin already initialized`	Two copies of the jar in `plugins/`	Delete the old one
Placeholders print raw, e.g. `%aquacore_version%`	PlaceholderAPI missing	Install PlaceholderAPI and restart
Colours show as `&x&1&2&3…`	Client below 1.16	HEX requires 1.16+