Export and import kit data

Permission: perplayerkit.admin. Works in game and from the console.

Export

/kitdata export <all|kitroom|publickits|playerkits> <file>

Written to plugins/PerPlayerKit/<file>.ppk; the plugin adds the extension. An existing file requires confirm to overwrite.

/kitdata export all season4-backup
/kitdata export kitroom crystal-kitroom
/kitdata export publickits ffa-kits

What each option includes

Option	Includes
`kitroom`	All saved kit room pages, including hidden pages, as last saved to the database. Run `/kitroom save` first if you edited the kit room. The export reads the database, not the editor.
`publickits`	Every public kit and its config entry: display name and menu icon. On import, the receiving server adds missing `publickits` entries to its own `config.yml` and updates existing ones. A kit in config that was never saved with `/savepublickit` carries over as a config entry with no contents.
`playerkits`	Every player kit and enderchest kit in the database.
`all`	Everything above, in one file.

Import

Put the in plugins/PerPlayerKit/, then:

/kitdata import season4-backup

If the import would replace anything it lists what and stops. Run it again with confirm:

/kitdata import season4-backup confirm

Kit room, public kits, and the kits of affected online players reload immediately. No restart.

How it behaves

Behavior	Detail
Any database to any database	Export from SQLite and import into MySQL, PostgreSQL, Redis, or YAML.
Checked before anything is written	`.ppk` carries a version number and a . Every kit is test-decoded before anything is written.
Locked to the plugin folder	Files are only read from and written to `plugins/PerPlayerKit/`. Names may use letters, numbers, dots, dashes, and underscores.
One at a time	Exports and imports never overlap.

A damaged file is rejected whole, never half-applied. Only import .ppk files from people you trust. Treat one like a plugin jar.

Common jobs

Hand a setup to another owner
Fill a test server
Keep an off-site copy

/kitroom save
/kitdata export kitroom my-kitroom
/kitdata export publickits my-publickits

Send both files; they drop them in plugins/PerPlayerKit/ and import each.

/kitdata export all prod-snapshot

Copy prod-snapshot.ppk to the test server and import it. Database types need not match.

/kitdata export all weekly-2026-08-21

Unlike automatic backups, this works on MySQL, PostgreSQL, and Redis too.

Which data tool do I want

Tool	Moves	Works on	Use it to
`/kitdata`	A file you carry	Every database	Move a setup to an unrelated server
`/perplayerkit migrate`	One database to another	Every database	Change database type on the same server
Automatic backups	Timed local snapshots	SQLite and YAML only	Recover from corruption or a mistake

Kit data exports contain kit definitions and contents. Remembered kit selections are included in full database backups and storage migrations. Exports include saved kit room pages even when kitroom.pages hides them. Increase that setting to show imported extra pages. Files containing pages beyond the first five require PerPlayerKit 1.8 or newer.

Start here

Features

Commands

Settings

Managing data

Common issues

For developers

Export and import kit data

Export

What each option includes

Import

How it behaves

Common jobs

Which data tool do I want

​Export

​What each option includes

​Import

​How it behaves

​Common jobs

​Which data tool do I want

Export

What each option includes

Import

How it behaves

Common jobs

Which data tool do I want