getting started.

everything you need to get havoc running in your server.

setting up

01
invite the bot
add havoc with the invite link. the default link requests basic chat and voice permissions, not administrator. add only the permissions needed for the modules you enable — see permissions & security for the module map.
02
move the role up
drag the havoc role near the top of your role list, just under your admin roles. the bot can only act on members and roles that sit below its own highest role. most "it did nothing" reports are this.
03
run the diagnostic
,setup checks havoc against your server and reports what is missing: permissions it does not have, and the two things it cannot create on its own. it changes nothing, so run it as often as you like.
04
create the jail setup
,setupmute builds the jail role and applies the channel overwrites needed for jail isolation. ,mute and ,timeout use discord’s native timeouts and do not need this setup; havoc needs moderate members and sufficient role hierarchy for those actions.
05
point logging somewhere
,log add #server-log moderation starts the paper trail. you can split events across several channels later; one channel is enough to begin.

two ways to type everything

most commands answer to both a text prefix and a slash command, reaching the same code either way. the prefix defaults to a comma. the slash name is not always the prefix name — commands that take a sub-action are grouped, so ,ban is /ban run and ,setup is /config setup. ,help <command> prints the exact slash path for whatever you are looking at.

,ban @member raiding
/ban run member: @member reason: raiding

a little over sixty commands are prefix only — mostly the economy and the longer conversational ones — and they have no slash form at all. the command list marks which is which, straight from the running bot.

if a comma clashes with another bot, change it for the server.

two ways to type everything commands
command	what it does	needs
/,prefix	show the prefix this server is using	anyone
/,prefix set !	change the server prefix	administrator
/,prefix self	drop the override and go back to the comma	administrator

finding your way around

,help lists every category. give it a category or a command and it narrows down to usage, aliases, and the permission a member needs to run it — the same data this site is built from, read straight out of the running bot.

,help
,help moderation
,help tempban

,config view prints the current settings for the whole server: prefix, logging routes, automod state, moderation behavior, and the roles havoc is using. it is the fastest way to answer "what is this server actually configured to do".

if slash commands are missing

discord caches an application's slash commands, and a freshly invited bot can take an hour to show its full list. the text prefix works immediately in the meantime. if a specific slash command never appears, check the troubleshooting page.

tipstart small

you do not need to configure every module. logging and moderation are worth ten minutes on day one; economy, music, and tickets can wait until someone asks for them.