Troubleshooting

• packet-adapter: UNAVAILABLE in /ff status: PacketEvents isn't installed, or failed to load before FlagForge (check console for its own startup lines). movement.timer.a/ packet.rate.a/packet.sequence.a register but stay inert; every other check is unaffected.
• Persistence: DISABLED: check console for the Invalid storage.yml: or connection-failure line logged at startup. Detection still runs; nothing is stored, and no preventable action can execute (ActionDispatcher requires storage).
• A check shows DISABLED (repeated internal errors) in /ff checks: it threw 5 consecutive exceptions and was auto-disabled to protect the server. This is a bug — please report it with the SEVERE console line — then /ff reload or /ff check <id> enable to give it a fresh start once fixed.
• Discord alerts never arrive but discord.enabled: true: /ff discord status shows whether a webhook URL actually resolved. alerts.yml never contains the raw secret — set FLAGFORGE_DISCORD_WEBHOOK_URL as an environment variable before starting the server (see Discord Staff Alerts).
• Plugin doesn't load at all: check for Unsupported API version in console — this means you're running a Minecraft version older than 1.21.10; FlagForge cannot load at all there (this is Paper's own gate, not FlagForge's). A newer mismatched version loads but logs Version check: MISMATCH and registers zero gameplay listeners until you set operating-mode.unsupported-version-override: true for development.
• A staff member can't run any /ff subcommand: confirm they (or their permission group) have at least flagforge.command.status; individual subcommands need their own listed permission even if the sender is an operator without a permissions plugin managing defaults correctly.