Permission loops that crash the server
If a lists b as a child and b lists a, Paper follows the chain until it runs out of stack. We tried it: the whole server went down at startup.
Check your plugin.yml before the server does.
Paste a plugin.yml or drop your plugin .jar. Permistry reads it the way a Paper server does and tells you in plain words what will break. Everything runs in your browser and nothing is uploaded.
plugin.yml
You can also drop a plugin.yml, paper-plugin.yml or .jar anywhere on the page.
What it checks
A plugin that depends on itself
Put your own plugin name in depend, softdepend or loadbefore and Paper 26.3 crashes before any world loads.
Typos the server ignores in silence
softdepends, alias, Permissions with a capital P. Unknown keys are skipped without a word. Permistry tells you which key you meant.
Command permissions that do not exist
The command checks homes.hmoe while the list has homes.home. Players get "no permission" and you get a bug report.
Everything that stops the plugin from loading
Spaces or reserved words in the name, depend written as text instead of a list, a bad load value, broken library coordinates, a main class missing from the jar.
Keys that cancel each other out
Two commands: blocks in one file? The server keeps the last one, and every command in the first block is gone.
Need a plugin built?
Kitebyte also writes custom plugins for Paper and Spigot servers, tested on a live server, with full source code. Fixed prices from $25. See packages and how ordering works.
Coming soon: Permistry Pro, a command-line and GitHub Action version of the checker for your CI, about $9 one-time. The web checker stays free.
Tested on a real server
Every rule was checked by loading broken plugins on Paper 26.3 (build 249). When the server prints an error, Permistry shows the same line, so you know what to look for in your logs. See what the server did in each case, or look up a specific error from your server log.