Direct answer

Use plugin-capable server software such as Paper, download a compatible plugin JAR from a trusted source, place it directly in the server's plugins folder, and restart the server. Then check the console or run /plugins to confirm it enabled.

Install a plugin step by step

  1. Stop the server.
  2. Download the plugin from its official page, Hangar, Modrinth, BukkitDev, or the author's GitHub when appropriate.
  3. If you downloaded a ZIP, extract it and identify the Paper/Bukkit JAR the author tells you to use.
  4. Place the JAR in plugins/, not in a subfolder.
  5. Start the server and read the startup log.
  6. Run /plugins in game as an operator, or plugins in the console.

Only install plugins you trust

Plugins can access the server machine.Paper warns that plugins have broad access to the server and its files. Do not install mystery JARs from reupload sites, chat attachments, or “cracked” bundles.

If the plugin is red or missing

Open logs/latest.log and search for the plugin name. Common causes include a missing dependency, unsupported Minecraft version, duplicate old and new plugin JARs, or downloading a Fabric/Forge mod instead of a Paper plugin.

An error mentioning UnknownDependencyException normally tells you which required plugin is missing.

Restart instead of using reload

Do not use Bukkit's general /reload as your normal plugin update workflow. Paper marks reload as deprecated because it is known to cause plugin problems. Stop and start the server cleanly instead.

Where plugin configuration appears

Most plugins create their data folder inside plugins/ after the first successful start. Stop the server before making major configuration edits unless the plugin's own documentation says a live reload command is supported.

Test the correct platform and dependencies
  1. Verify the JAR targets the actual plugin API (Paper/Spigot versus Velocity) and Minecraft version. Keep mod JARs in the mod loader’s directory, not plugins.
  2. Restart once and read the first relevant plugin startup error; missing hard dependencies, duplicate versions and unsupported Java are different problems.
  3. As a non-op player, test one intended command or feature and its permission. A green /plugins entry does not prove the plugin is configured or integrated correctly.

Official references

These references were checked while preparing this guide. Version-specific behavior can change, so use the project documentation for your exact release when a detail differs.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000