Install and update plugins
Check the source, Minecraft/Java version, and dependencies before enabling a plugin.
Choose a compatible build
Nusa preserves Bukkit/Spigot/Paper API signatures and one real main thread. Plugins using NMS, reflection, version-specific adapters, or packet pipelines still need a build suitable for 1.21.11. Successful enablement does not test every feature.
Use the author’s official source. Check Java 21 support, dependencies, and data migrations. Internal probe/benchmark JARs are test tools, not production plugins.
Install safely
- Back up configuration/data and coordinated external databases.
- Stop the server.
- Put the plugin JAR in
plugins/. Archive the previous version outside that directory to avoid duplicates. - Add required dependencies according to the plugin’s own documentation.
- Start, read errors, and run
nusa doctor. - Configure permissions and test real workflows on staging before production.
Do not substitute hot-loading or /reload for restart checks; plugins can retain tasks/listeners/resources.
Sensitive integrations
Doctor includes structural advisories for ProtocolLib, Citizens, WorldEdit, and FastAsyncWorldEdit. These are not lists of broken releases. Do not install alternative WorldEdit/FAWE providers together without explicit upstream support.
Inventory listeners can restore native hopper polling. Packet plugins can make shared encoding ineligible. Changed optimization opportunities do not necessarily indicate broken APIs.
Use doctor and plugin diagnosis for failures. Restore matching plugin data/database backups when reverting a migration; replacing only the old JAR may be insufficient.