Need Support?

Total Download reached
10 Thank you for downloading this plugin!
20 Wow thank you
30 Holy smokes Thanks
40 Dang Thanks so much
50
60
70
80

Version 6.0 is here! This will have a web dashboard!


If you get this message, ignore it. It is doing nothing and not hurting your server.
[HorriblePlayerLoginEventHack] You have plugins listening to the PlayerLoginEvent, this will cause re-configuration APIs to be unavailable:
This is from Paper they remove PlayerLogin Event.



[HR][/HR]

What PluginManager Is

PluginManager is made for server owners and staff who want a cleaner way to manage plugins without relying on guesswork, scattered notes, and risky live changes.

It gives you one place to review plugin health, check conflicts, handle safer reload decisions, work with configs and backups, and keep an eye on the server through both an in-game GUI and a web dashboard.

This is not just another /plugins replacement.

It is built for the kind of day-to-day admin work that actually takes time on a real server:

• checking what changed before a problem started
• figuring out which plugin needs attention
• deciding whether a reload is safe
• reviewing conflicts before they become player problems
• keeping staff on the same page during updates and maintenance

If your server has reached the point where plugin maintenance feels messy, PluginManager is meant to make that part of the job easier.

[HR][/HR]

Top 10 Features

1. In-game admin GUI
Open a full plugin management screen with /pm gui.

From there you can browse plugins, open detail views, check health, review conflicts, and work through admin tools without bouncing through a long chain of commands.

2. Web dashboard with staff accounts
PluginManager includes a web admin center with logins, staff roles, live server stats, diagnostics, file editing, and plugin action pages.

It is useful when you want a better workflow outside the Minecraft client, especially for owners and trusted staff.

3. Safer live plugin actions
Enable, disable, and reload actions come with more context before staff click anything.

Instead of guessing, your team can see things like trust signals, impact hints, reload safety, audit history, and maintenance controls first.

4. Real diagnostics for real server problems
PluginManager includes health views, conflict checks, startup diagnostics, activity tracking, scheduler insight, incident review, and deeper dashboard tools for lag hunting.

That makes it easier to answer questions like:

• what changed?
• which plugin looks like the problem?
• what is under pressure right now?
• what should not be reloaded live?

5. Recovery and maintenance tools
PluginManager also helps with the work around plugin actions, not just the actions themselves.

That includes:

• config review
• config editing
• backups
• restore tools
• removal previews
• maintenance planning
• notes and issue tracking

That makes it a lot more useful when something goes wrong and the team needs to work carefully.

6. Trust, impact, and reload safety checks
PluginManager does a better job of showing staff when they should slow down.

Instead of treating every plugin action the same, it gives you trust signals, impact hints, and reload safety guidance before somebody clicks the risky button.

7. Audit history that is actually useful
You can review who changed what, when it happened, and what the result was.

That matters a lot when something starts breaking and the first question is, "what changed?"

8. Config and file tools
PluginManager includes config review, config history, and a controlled file editor in the web dashboard.

That makes small config fixes and change review much easier without giving staff messy full-server access.

9. Better team workflow
The dashboard is built for more than one person.

With staff accounts, roles, approvals, ownership tracking, notes, and issue pages, it is much easier to keep a team lined up during updates, incidents, and routine maintenance.

10. Redstone and live problem tracking
PluginManager can help narrow live performance complaints down faster with tools like:

• tick spike review
• main-thread pressure
• async load watch
• redstone hotspot tracking

That gives staff a better starting point before they jump into deeper profiling.

[HR][/HR]

Description

Most servers eventually run into the same plugin-management problems:

• nobody remembers what changed
• reloads happen too quickly
• conflicts are found too late
• permissions and commands get messy
• staff do not have one shared view of what is safe and what is risky
• maintenance turns into guessing

PluginManager is built to help with that.

You can use it in a simple way and just open the GUI for health checks and plugin review, or you can go deeper and use the web dashboard for diagnostics, incident review, safer maintenance planning, ownership tracking, storage checks, account management, and staff workflows.

It works well for quick daily checks, but it is also built for the moments when something is actually wrong and the team needs better information before touching anything live.

A few simple examples:

• A staff member can open /pm gui, check health, and quickly spot which plugin needs a closer look.
• An admin can open the dashboard, check impact and trust signals, and decide whether a reload is actually a good idea.
• An owner can review updates, maintenance windows, backup freshness, and issue tracking from one place.

That is the real point of PluginManager:

• clearer information
• safer decisions
• better staff coordination
• less guesswork during maintenance

[HR][/HR]

Commands

Main command

• /pluginmanager
• Alias: /pm

PluginManager uses one main command with grouped subcommands. You do not need to memorize all of them on day one. Most servers end up using a smaller set regularly and only open the deeper tools when they actually need them.

Command List

• /pm gui
  Open the main in-game admin GUI.
  
• /pm list
  Shows the current plugin list.
  
• /pm info <plugin>
  Shows a closer breakdown for one plugin.
  
• /pm health
  Opens or prints plugin health information.
  
• /pm dashboard
  Shows dashboard information or the web panel entry details.

Live plugin actions

• /pm enable <plugin>
  Enables a plugin.
  
• /pm disable <plugin>
  Disables a plugin.
  
• /pm reload <plugin>
  Runs the plugin through the safer reload flow.
  
• /pm stage-restart <plugin>
  Marks a plugin for restart-based handling instead of forcing everything live.

Diagnostics and review

• /pm conflicts
  Reviews command, dependency, and permission conflicts.
  
• /pm diag
  Opens startup and diagnostic reporting tools.
  
• /pm audit
  Shows action history and tracked admin activity.
  
• /pm compat
  Reviews compatibility information.
  
• /pm deps
  Shows dependency-related information.
  
• /pm risk
  Reviews plugin risk and caution signals.
  
• /pm analytics
  Opens analytics and runtime insight tools.

Recovery and operations

• /pm data
  Opens plugin data and storage-related tools.
  
• /pm cleanup
  Reviews leftover files and cleanup targets.
  
• /pm uninstall
  Walks through plugin removal more carefully.
  
• /pm config
  Opens config-related tools.
  
• /pm notes
  Opens plugin notes tools.
  
• /pm profile
  Works with saved plugin or server profiles.
  
• /pm maintenance
  Opens maintenance-related tools and controls.

Safety and staff workflow

• /pm safemode
  Opens or changes safe mode controls.
  
• /pm quarantine
  Opens the quarantine review tools for plugins or jar files that were set aside because they looked unsafe, broken, or suspicious.
  
  This is where staff can see why something was blocked, decide whether it should stay quarantined, and work out whether it needs closer review, cleanup, or recovery.
  
• /pm gate
  Manages plugin gate and readiness controls.
  
• /pm notify
  Sends staff-facing notifications.
  
• /pm lang
  Works with language settings.

Where to start first

If you are new to the plugin, these are the best first commands to try:

1. /pm gui
2. /pm health
3. /pm conflicts
4. /pm audit
5. /pm dashboard

That gives you a quick feel for the main workflow without needing to learn everything at once.

[HR][/HR]

How To Use It

For a quick daily check

1. Run /pm gui
2. Open Health
3. Open Conflicts if something looks off
4. Open a plugin detail page if one plugin stands out

Before a risky reload

1. Open the plugin detail page
2. Review trust, health, and impact signals
3. Check whether reload looks safe
4. If it does not, stage it for restart instead

When players report lag

1. Open the web dashboard
2. Check server mood, TPS, and MSPT
3. Open pages like:
   • Tick spike timeline
   • Main-thread pressure
   • Async load watch
   • Slow reload report
4. Follow the action links into plugin detail or impact pages

During maintenance

1. Review audit history
2. Use the planner if work should happen later
3. Check trust and impact before making live changes
4. Use notes, issues, and profiles to keep the team lined up

[HR][/HR]

Permissions

Main permission groups

• pluginmanager.view.*
  View tools, health, audit, GUI, and dashboard access
  
• pluginmanager.operator.*
  Operator-level actions such as reload and stage-restart
  
• pluginmanager.admin.*
  Higher-risk actions such as enable, disable, uninstall, cleanup, profile, config, safety, and maintenance controls
  
• pluginmanager.*
  Full access

Default command permission

• pluginmanager.view.use

[HR][/HR]

Why Server Owners Use It

PluginManager is for owners who are tired of plugin maintenance feeling improvised.

It gives your team:

• better visibility
• safer live actions
• stronger diagnostics
• cleaner audit trails
• better staff workflow

If your server has moved past “just reload it and hope for the best”, this plugin is built for the next step after that.