documentation

getting started

raidworks gets invited like any other bot — the link will live on the work page once it's public. Once it's in your server, it needs a handful of permissions to actually do its job: Manage Roles, Manage Messages, Kick Members, and Ban Members cover moderation. Everything else just needs to see and send messages.

First command to run is /setup — it walks through picking a mod-log channel, a muted role, and which automod rules to turn on. Everything else works out of the box after that.

commands & api

Commands are grouped by what they actually do, rather than dumped in one long list.

• moderation — /ban, /kick, /mute, /warn, /case (look up a user's history)
• automod — spam and raid detection, filtered words, join-rate limiting
• utility — /userinfo, /serverinfo, /avatar
• config — /setup, /logs, /permissions

self-hosting

raidworks runs as a hosted service — invite it and it's live, no server or database to manage on your end. If a self-hostable version ever makes sense, real deployment notes will replace this paragraph instead of a promise with nothing behind it.

faq

is raidworks free to use?

Core moderation and utility commands are free. Anything beyond that will be clearly marked before it matters — no surprise paywalls mid-setup.

does it support slash commands?

Yes — everything is a slash command. No prefix to remember or accidentally trigger.

what data does it store?

Only what's needed to run moderation features — case logs, configured settings, that kind of thing. Specifics live in the privacy policy.

can I request a feature or report a bug?

Discord is fastest — @drinksinvegas. Email works too, see the contact section on the home page.