faq.

durable server configuration and feature state live in the instance’s PostgreSQL database. depending on what the server uses, that can include moderation cases, verification records, ticket records, economy balances, giveaway entries, saved playlists and configured channels, roles or logs. Discord still owns Discord messages, channels, roles and posts. records remain until the operator removes them.

ai only receives the message or command being handled plus the context that feature deliberately assembles, such as a short conversation history or public server configuration. it does not get a blanket copy of every channel. web lookups send the search query to the configured ai/search provider. check the instance operator’s policy before using ai for sensitive information.

yes. private-channel context is not replayed into a different channel unless the bot can confirm that the destination audience could already see the source. staff should still restrict havoc’s Discord channel permissions to only the rooms it needs, and can keep sensitive channels outside its access entirely.

a member starts from the server’s verification panel, confirms the Discord account in the browser, and returns to the server. the bot verifies the signed result, checks the server’s own rules and stored matches, then grants the configured member role only when every server-side check passes. the browser link itself is not permission to grant a role.

Discord commands, live moderation and new verification requests cannot run while the process is offline. durable records remain in PostgreSQL. when havoc returns, it restores persistent moderation state and catches up eligible scheduled work such as giveaway deadlines; live music playback and its in-memory queue do not continue through an outage.

supported punishment commands create a numbered case with the target, action, reason, actor and timing. configured logging routes can publish moderation events to a staff channel, while the dashboard exposes case history and active timed actions to authorized server staff. Discord audit logs remain a separate record controlled by Discord.

the Discord server’s permissions control who can change settings: most setup actions require administrator or manage server, and individual moderation commands check their matching Discord permission. havoc’s owner account can perform its own owner-only operations, but cannot bypass Discord role hierarchy or managed-role rules.

the server owner can remove havoc from Discord from Server Settings → Integrations → Bots and Apps, or revoke its roles and permissions. removal stops future access but does not automatically erase the operator’s database. ask the instance operator to delete that server’s stored records and backups. self-hosted operators should remove the server’s rows from PostgreSQL when they are ready to erase them.

havoc’s source does not contain a subscription or paid feature gate. running your own instance still means paying whatever your host and PostgreSQL provider charge, and ai calls depend on configured provider credentials. ask the operator of the particular instance you are inviting about its terms.

either model is possible. an existing instance is invited like any other Discord bot. a self-hosted instance needs Python 3.12 or newer, a Discord application and token, PostgreSQL, the server members and message content intents, and a process that stays online.

no. Discord commands are the primary interface, and the bot keeps running if its dashboard api cannot start. the dashboard is an optional browser view for configuration and bot state. see the dashboard guide for its scope.

run ,help for categories, then give it a category or exact command. it reports live usage, aliases and required permissions, so it is more reliable than guessing a subcommand.

the application must be invited with the applications.commands scope, and its operator must publish the command tree. Discord’s global command cache can then take time to update. prefix commands do not depend on that tree and work while the slash list catches up.

yes. ,prefix set ! changes the server prefix and requires administrator. ,prefix self ; sets a personal prefix and, despite the name, also requires administrator in the live registry. run ,prefix to inspect the current server prefix.

not for every feature. administrator makes initial setup simpler, but each command checks its listed Discord permission. the bot itself still needs the channel and action permissions required by the feature. for example, logging needs view channel, embed links and manage webhooks in its destination.

Discord role order is separate from permissions. both the staff member and havoc must rank above the target, and havoc cannot modify managed roles, the default role or the server owner. move havoc’s highest role above the members and roles it must manage.

yes. choose a different prefix if text commands collide, and avoid configuring two automod systems to punish the same message. logging and moderation actions from another bot can still appear as Discord events, so route and ignore rules deliberately.

configuration and durable feature state live in PostgreSQL, selected with the operator’s database connection setting. this includes settings, ticket records, giveaway entries and deadlines, economy balances, cases and saved music playlists. Discord still stores channels, messages, roles and posts.

live music playback and its in-memory queue stop. short-lived caches such as deleted-message snipes are also memory-bound. saved playlists remain. tickets and giveaway buttons are registered by stable component ids, and their records remain in the database, so a normal restart does not invalidate them.

it cannot talk to Discord while offline. persisted giveaway deadlines are caught up when it returns, with entries retained and settlement guarded against duplicate draws. persistent moderation state is restored on startup. music cannot continue because its voice connection is not durable.

the default is one open ticket. staff can set ticket limit <count> from 1 through 10. this is a per-member open-ticket limit, not a promise that Discord will allow unlimited channels.

a giveaway can run from 10 seconds through 60 days, draw at most 20 winners, use a prize up to 250 characters, and retain at most 10,000 entrants. ,giveaway view 12 shows one stored draw and its entry count.

balances, banks, inventories, jobs, trades and leaderboards are stored per server. economy commands are prefix-only, so use the server’s current prefix rather than looking for slash entries. gambling can lose currency, and owner-only reset commands can wipe a member or the whole server economy.

confirm the prefix with ,prefix, then use ,help to verify the command exists. havoc ignores unknown prefix text. if a real command is silent, check that havoc is online and can view and send in that channel; then follow the troubleshooting checks.

give the instance operator the exact command form, server and channel ids, approximate time, the visible error text, and whether prefix and slash forms differ. do not send bot tokens, database urls, webhook credentials or private ticket contents. a reproducible command and error is more useful than “it broke.”