PluginVersions Guide

This page introduces PluginVersions as a public staff guide. It focuses on what the tool does, how authorized staff get started, and which commands are useful.

What It Does

Plugin version inventory, declared dependency/dependent reports, tested Java/server/dependency gate, URL curation, and Markdown/Discord exports.

How Staff Use It

Use /pv list to inspect versions, then /pv depend CMILib, Vault, ProtocolLib, or ViaVersion to see declared relationships. Review required, optional, and indirect dependents before testing a removal. The report does not establish whether an integration is active or a plugin is safe to uninstall.

Available features include:

• A searchable inventory of loaded plugins, versions, enabled state, and curated project links.
• Declared dependency reports with required and optional dependents, indirect required chains, aliases, and load-order references.
• A tested Java, Paper, CMI, CMILib, and dependency compatibility gate.
• Plugin and server summaries for post-update support checks.
• A persistent plugin inventory database with optional refresh behavior.
• Manual source, download, documentation, and support URL curation.
• URL audits that highlight missing or malformed project links.
• Full Markdown and compact Discord-friendly export reports.

Reading a Dependency Report

| Category | What it means | | --- | --- | | Required by | Plugins that declare the target as required to load. | | Optional integration for | Plugins that may lose features without the target. Active use is not confirmed. | | Indirectly required by | A shortest chain of required dependencies leading to the target. | | Depends on | Required and optional dependencies declared by the target itself. | | Load-order references | Ordering declarations, not proof of API use. |

Names and provided aliases match case-insensitively. Conflicting aliases are reported, and missing declared targets remain queryable. The report reads a fresh runtime snapshot and does not modify plugins or the inventory database.

Quick Start

1. Run /pv list to find the current plugin names and versions.
2. Run /pv depend CMILib or /pv depend Vault to inspect a dependency report.
3. Use /pv depend CMILib 2 for the next player page. Console receives the full report.
4. Review required chains and optional features, then test any removal with a full restart on the test server.

Commands

Command	What it does	Example
/pv	Opens or shows the main PluginVersions player view.	/pv
/pv info	Shows a friendly explanation of what PluginVersions does.	/pv info
/pv help [page|topic]	Shows the PluginVersions commands available to you.	/pv help
/pv list [page]	Lists available PluginVersions entries.	/pv list
/pv depend <plugin> [page]	Shows the target version/state, declared required and optional dependents, indirect required chains, its own dependencies, and load-order references. Does not certify safe removal.	/pv depend CMILib
/pv gate [page]	Runs the PluginVersions gate action.	/pv gate
/pv help overview	Shows the PluginVersions commands available to you.	/pv help overview
/pv help commands	Shows the PluginVersions commands available to you.	/pv help commands
/pv help gate	Shows the PluginVersions commands available to you.	/pv help gate
/pv help set	Shows the PluginVersions commands available to you.	/pv help set

Examples

• /pv info
• /pv list
• /pv list 2
• /pv depend CMILib
• /pv depend Vault
• /pv depend ProtocolLib
• /pv depend ViaVersion
• /pv depend CMILib 2
• /pv gate
• /pv set database.update-on-list false

Good To Know

• Dependency reports require pluginversions.depend, which defaults to op and is included in pluginversions.*. Use /pv depend, without an admin subcommand.
• Enabled/disabled describes Paper plugin state, not whether each optional feature is active.
• No declared dependents does not mean unused or safe to remove. ViaVersion can serve player connections even without plugin dependents.
• Runtime metadata excludes unloaded JARs, undeclared hooks, embedded libraries, and some Paper declarations (bootstrap-only or join-classpath: false).
• See the full administration reference for report scope and interpretation.

Full Reference

The full synced PluginVersions reference is available for exact technical details.