Direct answer

Create a separate staging instance with the same server build and a safe copy of plugin configuration and world data, then reproduce the feature without writing into production storage.

Recommended procedure

  1. Copy the currently deployed plugin list and exact versions, masking secrets such as database passwords and API tokens.
  2. Use a separate port and storage directory, with network access restricted to testers.
  3. Install only the new plugin and its documented dependencies; restart and inspect logs/latest.log for load errors or conflicting commands.
  4. Test critical permissions, player join/quit, inventory changes, protection and rollback with a non-operator account.

What to do next

Profile the new plugin under its real workload, document required configuration and keep the old production JAR/configuration for rollback.

How to verify the result

Approve deployment only after startup, gameplay, permission and storage checks all pass.

Version and compatibility notes

Do not connect a staging plugin to the live economy or moderation database unless explicitly designed for that safe read-only workflow. Plugin reload commands are not reliable substitutes for a full startup test.

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