This is a PlugMan *Fork*

PlugMan

PlugMan is a simple, easy to use plugin that lets server admins manage plugins from either in-game or console without the need to restart the server.

Features

• Enable, disable, restart, load, reload, and unload plugins from in-game or console.
• List plugins alphabetically, with version if specified.
• Get useful information on plugins such as commands, version, author(s), etc.
• Easily manage plugins without having to constantly restart your server.
• List commands a plugin has registered.
• Find the plugin a command is registered to.
• Tab completion for command names and plugin names.
• Dump plugin list with versions to a file.
• Check if a plugin is up-to-date with dev.bukkit.org
• Permissions Support - All commands default to OP.

Commands

Command	Description
/plugman help	Show help information.
/plugman list [-v]	List plugins in alphabetical order. Use "-v" to include versions.
/plugman info [plugin]	Displays information about a plugin.
/plugman dump	Dump plugin names and version to a file.
/plugman usage [plugin]	List commands that a plugin has registered.
/plugman lookup [command]	Find the plugin a command is registered to.
/plugman enable [plugin|all]	Enable a plugin.
/plugman disable [plugin|all]	Disable a plugin.
/plugman restart [plugin|all]	Restart (disable/enable) a plugin.
/plugman load [plugin]	Load a plugin.
/plugman reload [plugin|all]	Reload (unload/load) a plugin.
/plugman unload [plugin]	Unload a plugin.
/plugman check [plugin|all] [-f]	Check if a plugin is up-to-date.

Permissions

Permission Node	Default	Description
plugman.admin	OP	Allows use of all PlugMan commands.
plugman.update	OP	Allows user to see update messages.
plugman.help	OP	Allow use of the help command.
plugman.list	OP	Allow use of the list command.
plugman.info	OP	Allow use of the info command.
plugman.dump	OP	Allow use of the dump command.
plugman.usage	OP	Allow use of the usage command.
plugman.lookup	OP	Allow use of the lookup command.
plugman.enable	OP	Allow use of the enable command.
plugman.enable.all	OP	Allow use of the enable all command.
plugman.disable	OP	Allow use of the disable command.
plugman.disable.all	OP	Allow use of the disable all command.
plugman.restart	OP	Allow use of the restart command.
plugman.restart.all	OP	Allow use of the restart all command.
plugman.load	OP	Allow use of the load command.
plugman.reload	OP	Allow use of the reload command.
plugman.reload.all	OP	Allow use of the reload all command.
plugman.unload	OP	Allow use of the unload command.
plugman.check	OP	Allow use of the check command.
plugman.check.all	OP	Allow use of the check command.

Configuration

File	URL
config.yml	https://github.com/Test-Account666/PlugManX/blob/master/plugman-core/src/main/resources/config.yml

Building

Build Instructions

Building PlugManX is simple:

0. Use JDK 21 for Maven plugman-paper initialization requires Java 17 or above, and the project compiler is configured for Java 21. In practice, run all Maven commands with JDK 21.

   PowerShell:

   $env:JAVA_HOME = "C:\Path\To\jdk-21"
   $env:Path = "$env:JAVA_HOME\bin;$env:Path"
   java -version
   mvn -version

1. Clone the repository:

   git clone https://github.com/Test-Account666/PlugManX.git
   cd PlugManX

2. Initialize the root project

   mvn install -N

3. Initialize Paper NMS artifacts plugman-paper depends on generated paper-nms artifacts. This step is required before the full reactor build.

   Bash:

   cd plugman-paper
   mvn paper-nms:init
   cd ..

   PowerShell:

   Set-Location plugman-paper
   mvn paper-nms:init
   Set-Location ..

4. Build the project:

   mvn clean install

5. Find the built artifacts:

   • Individual module JARs will be in each module's target/ directory
   • The assembled distribution will be in plugman-assembly/target/

Troubleshooting

• If mvn paper-nms:init fails with "outdated Java version", Maven is not using Java 17+ yet. Switch JAVA_HOME to JDK 21 and verify with mvn -version.
• If plugman-paper fails to resolve ca.bkaw:paper-nms, make sure mvn paper-nms:init completed successfully inside plugman-paper before running mvn clean install.
• If Maven says the dependency "was not found during a previous attempt", force a refresh with mvn -U clean install.
• If the cached failure still blocks the build, delete the local snapshot cache and initialize again:

Remove-Item -Recurse -Force "$env:USERPROFILE\.m2\repository\ca\bkaw\paper-nms\1.21.8-SNAPSHOT"
Set-Location plugman-paper
mvn paper-nms:init
Set-Location ..
mvn -U clean install

Version Management

PlugManX uses a centralized version property for easy version management across all modules. To update the version:

1. Edit the <plugman.version> property in the root pom.xml file
2. The version will automatically be updated in all modules and resource files during build

Current version is managed by the plugman.version property in the parent POM.

Developers

How to include PlugMan with Maven:

<repositories>
    <!-- PlugMan -->
    <repository>
        <id>PlugManX</id>
        <url>https://raw.githubusercontent.com/Test-Account666/PlugManX/repository/</url>
    </repository>
</repositories>

<dependencies>
<dependency>
    <groupId>com.rylinaux</groupId>
    <artifactId>PlugManX</artifactId>
    <version>${plugman.version}</version>
    <scope>provided</scope>
</dependency>
</dependencies>

How to include PlugMan with Gradle:

repositories {
    maven {
        name = 'PlugManX'
        url = 'https://raw.githubusercontent.com/Test-Account666/PlugManX/repository/'
    }
}
dependencies {
    compileOnly 'com.rylinaux:PlugManX:${plugman.version}'
}

License

This project is a fork of PlugMan (Link no longer works) and is distributed under the same license: LICENSE.