Setup & Config

A guided checklist that asks about every feature, then activates the bot. Start here.

🔒 Requires Manage Server

/setup

Walks through each feature area one at a time: mod roles, welcomes, mod log, automod, levels, Pokémon spawns, shop, tickets, suggestions, Hall of Fame and the rest, with what each one does and why you might want it. Skipping is an answer and is recorded, so the checklist stays honest and you can come back to anything later. The list is filtered by persona: AQWired is asked only about the AQW pieces, Omni about everything else.

Every setting directly, when you already know what you want to change.

🔒 Requires Manage Server

/config

The same editors /setup walks you through, reachable straight away and paginated by area. Sections are gated per persona. Community → Ambient Responses is where the bot stops chiming in on its own: the reply when somebody edits a message, the /mod cmd word triggers, the !name image commands, and currency for being reacted to. All four are on by default and switch off server-wide, which is what /mod blacklist could never do: that silences one channel at a time and takes muzzle, parrot and level-up announcements with it.

Bot Profile panel. Customise name, emoji, footer, avatar and banner per server.

🔒 Requires Manage Server

/botsettings

Posts the AQW account-verification button. The one prefix command AQWired keeps.

🔒 Requires Manage Server or a mod role

<prefix>setupverify

Run it in the channel that should hold the embed; your command message is deleted afterwards. It used to check for a role named exactly Mods and ignored the roles set in /setup, so in a server without that exact role nobody could run it, owner included. It now takes Manage Server or a configured mod role, the same rule as every other staff command. What the button grants is configurable per server, and the posted embed rewrites itself within a minute when you change it, so it can no longer promise roles it does not hand out. Super Premium servers can also post it from the web panel. See /verify.

Mod tools around the verify button: sweep unverified members by DM, check status.

🔒 Requires Manage Server or a mod role

The roles verification grants are per-server config now, edited in /config → Verifier Guilds: the verified role, the visitor role given to members outside the home guild (or switched off entirely), the unverified role it removes, which AQW guild counts as home, and the AQW guild → role combos. Verifying gives the verified role, that member’s guild role if a combo is set up for it, and the visitor role unless they’re in the home guild. So a home member gets the home role alone, and an ally gets the visitor role plus theirs. Left blank, everything falls back to the original behaviour: roles named Verified/Crows/Unverified with Ravens as home, and a built-in ally list paired by role name, so the Ravens server needs no setup and other servers no longer inherit its names.