Add PerPlayerKit as a dependency

PerPlayerKit is not on a public Maven repository. Add the jar by hand. PerPlayerKit is not on a public Maven repository. Add the jar by hand.

Put the jar in your project

Copy PerPlayerKit-x.x.x.jar into a lib/ folder in your project root.

Declare it in pom.xml

pom.xml

<dependency>
    <groupId>com.local</groupId>
    <artifactId>PerPlayerKit</artifactId>
    <version>local</version>
    <scope>system</scope>
    <systemPath>${project.basedir}/lib/PerPlayerKit-x.x.x.jar</systemPath>
</dependency>

Change the filename to match the jar you copied.

Declare it in plugin.yml

plugin.yml

name: ExamplePlugin
version: 1.0
main: com.example.ExamplePlugin
api-version: 1.19
depend:
  - PerPlayerKit

Paper now loads PerPlayerKit before your plugin.

If PerPlayerKit is optional for you, use softdepend instead, and guard your code with Bukkit.getPluginManager().isPluginEnabled("PerPlayerKit").

Build notes

The list from getPublicKits() is a copy, so iterating or modifying it never touches PerPlayerKit’s own data. The PublicKit objects inside it are the live objects. Treat them as read-only. The dependency is , so the jar is not bundled into your build. Paper resolves PerPlayerKit at runtime through the depend entry.

A system-scoped dependency does not warn you at build time when the server runs a different version than the jar in lib/. Re-check your integration on every PerPlayerKit update.

Start here

Features

Commands

Settings

Managing data

Common issues

For developers

Add PerPlayerKit as a dependency

Build notes

​Build notes

Build notes