configuration.

,setup is a diagnostic, not an automatic server builder. it reports whether havoc is missing the bot permissions needed for roles, channels, messages, bans, kicks, timeouts, and nicknames. it also reminds you to place havoc above managed members, enable the required developer-portal intents, run setupmute for jail, and configure private logging separately.

,setup
/config setup

config views inspect stored entries without printing private values. output uses a namespace and key followed by “configured”; it does not disclose afk text, message content, or saved role snapshots. the plain config path and config view read the server’s stored settings, while focused paths filter that list.

the antinuke branch manages the ids allowed to perform antinuke-protected actions. it requires administrator and is restricted to the server owner. add and remove resolve a current server member; list prints stored numeric ids. keeping this list short preserves the purpose of the protection.

,config antinuke add @trusted-admin
,config antinuke list
,config antinuke remove @trusted-admin

setupmute looks for a role named havoc jailed and a text channel named havoc-jail, creating either when absent. it gives the role access to that channel, hides every other channel from it, removes voice connect access, and stores the role and channel ids. the role must remain below havoc’s highest role.

mute uses discord’s native timeout and is capped at 28 days. jail uses the configured role and channel. re-runsetupmute after adding channels if the jail role’s overwrites do not isolate them as intended.

core configuration also includes the server prefix and command restrictions. prefixes are 1–12 characters, cannot contain whitespace or @, and require administrator to change. restrictions require manage server and add a role gate without replacing each command’s native discord permission.

,prefix
,prefix set !
,restrictcommand add "config view" @administrator
,restrictcommand list

prefix self currently removes the stored server prefix override and returns the server to the default comma; it does not persist a member-specific prefix. restriction reset clears every command gate, so list and record the current policy before using it.

havoc stores settings in its database under a server id, namespace, and key. values are persisted rather than held only in process memory, so ordinary bot restarts do not discard configuration. server ids keep one server’s settings separate from another’s even when the same administrator manages both.

several modules own their own namespaces. that is why a core config view can show that something is configured without exposing its value, and why a core reset deliberately does not erase every domain. use the relevant module guide—such as logging or automod—for its editing commands.

,config reset deletes the server’s config and restrictions namespaces. it retains moderation cases, restoration state, pending jobs, and settings owned by other domains. this is a core reset, not a factory reset.

,config view
,restrictcommand list
,config reset