Skip to content
Browse the docs

Getting started

Setting up Miwi

Invite Miwi, run /setup and walk through every module with menus.

Miwi is set up from Discord with menus โ€” no long commands to remember, and every change is saved the moment you make it.

1. Invite Miwi#

Add Miwi from the invite page. Keep the permissions it asks for: they are exactly what its features use, and never Administrator by default.

Then open Server Settings โ†’ Roles and drag Miwi's role near the top. Miwi can only manage members and roles that are below its own role โ€” this is the most common reason something "doesn't work".

2. Run /setup#

First, Miwi checks its own role. If any role is above Miwi, or it's missing a permission its modules need, setup shows exactly which roles and permissions to fix, with a Check again button that continues where you were.

Run /setup (or m!setup) in any channel. The first time, Miwi offers a guided setup that walks through every module, one menu at a time:

  1. Server settings โ€” prefix, manager roles, dashboard access, ignored channels
  2. Anti-raid โ€” join-flood detection and what happens to raiders
  3. AutoMod โ€” spam, links, invites, mass mentions and more
  4. Moderation โ€” DMs, required reasons, warning expiry, mod logs
  5. Logging โ€” a channel for every kind of log
  6. Tickets โ€” private support channels
  7. Welcome โ€” welcome, leave, boost and DM messages
  8. Role automation โ€” autoroles, sticky roles and voice roles

Each menu lists every setting with its current value. Pick a setting from the dropdown:

Setting typeWhat happens
Channel, category, role, userA picker opens with the current value already selected
On/off switchIt flips straight away
Text or a numberA form opens, filled in with the current value
A choiceA short dropdown opens

Channels and categories often have Create one for me, which makes a private channel for you. Role pickers have Create role: name it, and Miwi creates a role with no permissions right under its own role (or under yours, if that's lower) and picks it. Press Next to move on, Back to go back, or Stop guided setup to finish later โ€” /setup picks up where you left off.

3. Protect the server#

Antinuke has its own setup because it's the most important one: run /antinuke enable as the server owner. It starts in test mode, so Miwi only reports what it would do until you are ready. See Antinuke.

Running /setup again#

Once Miwi is set up, /setup asks what you want to do:

OptionWhat it does
Edit current setupOpens a list of every module so you can change a few things
Run guided setup againWalks through every module, keeping what you already set
Reset & start freshClears Miwi's settings and starts the guided setup from scratch

Reset can only be used by the server owner or an Administrator, and shows exactly what will change first. It never touches antinuke and the whitelist, cases and warnings, tickets and transcripts, AutoMod rules, giveaways, join-to-create hubs or Premium.

Jump straight to one module#

Every module has its own menu too:

ModuleCommand
Server settings/settings setup
Anti-raid/raid setup
AutoMod/automod setup
Moderation/moderation setup
Logging/logging setup
Tickets/ticket setup
Welcome/welcome setup
Role automation/autorole setup (also /stickyroles setup, /vcrole setup)

Or use /setup module: โ€” for example m!setup tickets.

Who can use the setup menus#

Setup menus need Manage Server (or a Miwi manager role). Only the person who opened a menu can click it. Changing manager roles and dashboard access needs the server owner or an Administrator.

Still stuck? Ask in the support server โ€” real people answer.

Setting up Miwi ยท Docs ยท Miwi