FAQ

The bot is not responding to a command. Why?

In rough order of likelihood:

1. The plugin is not enabled. A plugin only runs if its block exists under plugins: in your config - even an empty plugins.utilities: {} counts. The Diagnostics page flags this.
2. Your level is too low. Most moderation commands need level 50. Check the levels: section and the per-command overrides.
3. A command override or lockdown blocks it. Setup → Access & Permissions has a "Would it run?" resolver that tells you exactly which rule decided.
4. Wrong prefix. The prefix is per-server (commands.prefix).
5. A feature grant is missing. Some systems (music, image scanning, and others) are gated by feature flags. The dashboard shows a lock banner on anything your server does not have.

How do I get HepBoat in my server?

Through the shop on the dashboard: sign in with Discord, invite the bot, and buy access for your server - it's sold in 30-day blocks, and you can top up any time with the new time stacking on what's left. The shop shows the current price. The bot activates as soon as the payment clears. If the paid time ever runs out the bot pauses for that server - nothing is deleted, and it picks up where it left off the moment you add time again.

Something is broken mid-incident. Can I turn one thing off?

Yes - that is the point of the design. Removing a plugin's block from your config disables it live, and a paused plugin stops completely (commands and listeners both).

Where did my config change go? / Who changed the config?

Every config write - dashboard or command - creates a history entry (Config → History) with a diff, the author, and one-click restore. Config changes also emit a CONFIG_UPDATE mod-log event if you subscribe a channel to it.

Can I start my config over from scratch?

Yes, if you are the server owner - and only the owner, dashboard admins cannot. At the bottom of Config there is a "Wipe config to defaults" button that resets the entire configuration to the fresh-install template after you type the server ID to confirm. It only touches configuration: infractions, tags, XP, and message history all stay. The config you wiped lands in Config → History, so you can restore it if you change your mind.

Do timed punishments survive restarts?

Yes. Tempmutes, tempbans and timeouts are stored with their expiry and are reversed by a background sweep; a restart delays nothing.

Can banned users appeal?

If you enable appeals (infractions plugin + the APPEALS feature), a banned user gets an appeal link, fills in your custom form, and the submission lands in your dashboard's review queue with approve/deny actions.

Is my data mine?

Yes. Infractions can be exported as JSON with an export-scoped API key, and imported into another server with import. Message archives generated by purges expire automatically (7 days by default).