Direct answer

The plugins/ directory usually contains server-plugin JAR files and plugin-created data folders. Some plugins also store data in external SQL databases or other paths.

Step-by-step procedure

  1. Stop the server before manually editing persistent plugin data, unless the plugin specifically supports live editing.
  2. Identify each JAR and matching data folder; read the plugin’s own config and data-storage documentation before removing files.
  3. Back up both plugins/ and any external database used by permissions, economy, claims or inventories.
  4. For migration, restore the same plugin version and configuration in staging, then run a feature test before upgrading.

Common mistakes and trade-offs

Deleting a plugin folder can reset player balances, home locations, claims or permissions. Deleting only its JAR may leave orphaned configuration and data behind.

How to verify it worked

Check startup logs for database connection errors, then confirm a test setting or player record survives a graceful restart.

Version and platform differences

Fabric/Forge/NeoForge mods belong to mods/; Velocity has its own proxy plugins/. Do not blindly merge data folders across platforms.

Official references

These sources were checked for the current MSH revision. Version-sensitive details should always be confirmed against the project documentation for the release you run.

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