Direct answer

A plugin shown in red in /plugins is disabled, but the name alone does not explain why. Read the first meaningful startup error for that plugin and identify missing dependencies, invalid configuration or incompatible server APIs.

What it means

Bukkit-family plugin managers list installed plugins whether or not they enabled successfully. A JAR may exist on disk yet be disabled because an error occurred during load or enable.

Practical example: Example: UnknownDependencyException points to a required plugin that did not load; UnsupportedClassVersionError points to a Java/runtime mismatch; NoClassDefFoundError may indicate missing or incompatible dependencies. Those errors require different fixes. Follow the first exception around plugin enable, not the display color alone.

If you are a player

  • Record the plugin name and the exact feature or command that stopped working.
  • Do not copy an arbitrary replacement JAR from an unofficial download site.
  • Tell staff whether the plugin worked before a specific update.

If you run the server

  1. Read logs/latest.log from the top of the plugin load failure, not just the final Disabling line.
  2. Check the plugin’s required Minecraft/server and Java versions, plus required plugin dependencies.
  3. Confirm it belongs in the Bukkit/Paper plugins folder rather than Velocity plugins or Fabric mods.
  4. On a staging copy, restore the last working version with matching config/data if a migration failed.
  5. Restart cleanly and test the plugin’s real command/feature, not only the /plugins color.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

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