Skip to main content

About the plugin

Both, 1.19 or newer. Prefer Paper.
Yes, and open source under the .
Both optional. adds per-region kits for rekit on kill; adds placeholders in messages.
Two kit plugins fight over the same commands. Remove or rename the other. Coming from KitsX? Import your data.

Setting it up

One server: SQLite. A network: MySQL, PostgreSQL, or Redis. Never yml. See Storage and databases.
Yes. One command copies everything while the server stays online. See Change database.
Yes. /perplayerkit autosetup fills the kit room and the bundled public kits. See Set up your kit room.
/kit, then the nether star. /kitroom takes only save and load.
Nine by default, up to 99 via kits.max-slots. Needs a full restart. See Kits.
perplayerkit.admin grants admin tools and staff inspection. Give admins perplayerkit.use as well. See Give out permissions.

Running it

item-filter.enabled: true with kit-room-only: true filters loaded copies against your kit room. Stored definitions are preserved. See Anti-exploit.
Set broadcasts.enabled: false. For finer control, see Messages and broadcasts.
Kits belong to a : run /transferkits <newname> from the old account with both online, and the new account clicks [ACCEPT]. See Sharing and transfers.
Take it out of the kit room, enable item-filter with kit-room-only: true, then run /purgeitem <item> all confirm. See Remove a banned item.
config.yml
Fourteen ship with the plugin; set language in config.yml. See Languages.

Data and safety

SQLite and YAML: hourly, daily, weekly, monthly. Otherwise use your database’s own tools or /kitdata export all. See Backups.
Send the file and they import it. See Export and import.
Yes. Stop the server, swap the jar, start it again. Back up first on a dev build.

Still not answered

Troubleshooting

Longer fixes for specific problems.

Ask in Discord

The developer and other owners.