FAQ

FAQ / Troubleshooting

A module isn't doing anything after I set it to true. Did you run /plainbase reload or restart the server afterwards? config.yml changes are only read on startup/reload, never live-watched.

I'm getting an "OUTDATED CONFIG" warning. That's expected after updating the plugin if a config file's structure changed between versions. It does not mean the module is broken — it keeps running with your existing values. See Configuration & Versioning for exactly what the warning means and how to update your file.

Why does my OP keep getting a red config warning on join? Every OP gets this on every join for every config file that's below the version the installed jar expects. It's meant to be persistent/annoying on purpose so it doesn't get ignored — fix the config (see above) and it stops.

Can I use PlainBase on Spigot/Bukkit (no Paper)? No. PlainBase relies on Paper-only APIs (Brigadier command registration via the Lifecycle API, region schedulers for Folia-compatibility) and will not work on plain Spigot/Bukkit.

Does PlainBase support Folia? Yes — all scheduling (teleports, broadcasts, countdowns) goes through Paper's region/entity schedulers rather than the classic Bukkit scheduler, specifically so it also works correctly on Folia.

My server crashed/lagged — is it the Moderation module's database? The Moderation module defaults to a local SQLite file with connection pooling; this should be lightweight for typical server sizes. If you switched to MySQL, double check host/port/credentials in modules/moderation.yml — a misconfigured MySQL connection will show up in your server console at startup.

A ban issued on one server isn't blocking the login on another server. That only works if all connected servers point at the same MySQL database with storage.type: mysql in modules/moderation.yml — the default SQLite backend is local to a single server only.

Where do I report a bug or request a feature? Open an issue on GitHub.