Direct answer

Plugin removal can leave player metadata, persistent database tables, placeholder hooks or world objects. Back up everything first, then remove only what you understand.

Recommended procedure

  1. Write down which other plugins depend on the target using documentation and startup logs.
  2. Create a full server backup plus a copy of the specific plugin directory and any external database export.
  3. On a test instance, shut down and remove the plugin JAR; keep its data folder temporarily instead of deleting it immediately.
  4. Restart and inspect errors from dependent plugins, commands and world data.

What to do next

Replace or remove dependent integrations in a controlled order. For a protection plugin, inventory plugin or custom item provider, research migration needs before touching live data.

How to verify the result

Confirm startup has no missing dependencies and gameplay data survives, then archive rather than destroy the old plugin folder.

Version and compatibility notes

Deleting a plugin JAR does not necessarily remove its saved state. Conversely, deleting data may make rollback impossible. Do not run general-purpose cleanup commands that remove unknown tags or database schemas.

Official references

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