Skip to main content
Version: Next 🚧

Troubleshooting

The plugin does not appear in /plugins​

It failed to load. The reason is in the console at startup, above the first player join. Usual causes:

  • Wrong Java version — see Requirements.
  • Wrong server software — a Paper-only build will not load on Spigot.
  • Corrupt download — re-download; a truncated jar throws ZipException or Invalid plugin.yml.

Commands return "You do not have permission"​

The node is not granted. See Permissions. Being an operator does not grant nodes whose default is not op if a permission plugin overrides them — check with your permission plugin's own verify command.

Placeholders show as literal text​

%projectone_count% appearing verbatim means either PlaceholderAPI is not installed, or the plugin reading it does not support placeholders. Confirm with /papi parse me %projectone_count%.

Changes to config.yml do nothing​

  • Run /projectone reload.
  • Storage settings need a full restart, not a reload.
  • Check the console for a YAML parse error — an invalid file falls back to the previous values. Indentation with tabs is the usual culprit; YAML requires spaces.

Errors mentioning region threads​

On Folia, work touching the world must run on the owning region's thread. If a stack trace mentions the wrong thread, and you are calling into this plugin from your own code, see Developer API.

Reporting a bug​

Include:

  1. Plugin version, and the exact output of /version.
  2. Server software and version.
  3. Java version.
  4. The full stack trace from the console, not a screenshot of part of it.
  5. Your config.yml, with passwords removed.
  6. Output with debug: true set.

A report without the server version and stack trace cannot usually be acted on. Saying so up front saves a round trip.