Skip to main content
Lucie protects your server in layers: detection configurable from the web dashboard, to isolate suspicious accounts, a global ban system shared across every server Lucie is in, and new-member verification. Here are the commands that control each piece.

​
The flow in short

  1. Configure anti-raid and verification in the web dashboard (joins-per-minute threshold, action to apply, invite pausing, etc.).
  2. Diagnose with !check that Lucie has the permissions and protections she needs.
  3. If you see a raid coming, turn on raid mode with !raidmode: joins are treated as a raid according to what you have configured in the panel.
  4. Isolate suspicious accounts with !quarantine (and revert with !unquarantine).
  5. Escalate confirmed raiders with !banraid: a ban on your server plus a report to the Lucie team, who decide whether it becomes a global ban.
  6. Verification filters new members with a button in the channel you configure.
The fine-grained configuration (thresholds, actions, basic or captcha verification…) lives in the web dashboard: lucie.elxy.dev → your server → Anti-raid. The commands on this page are the emergency and maintenance controls.

​
!raidmode

Turns on raid mode manually, as a preventive measure: while it is active, Lucie treats server joins as part of a raid and applies the action you have configured in the panel. End it with !raidmode off. Usage: !raidmode [off] Aliases: modoraid Permissions: Administrator or Manage Server (or being the server owner) Examples
Handy when you get word of an incoming raid (announced in another server, for example) and don’t want to wait for automatic detection to trigger.

​
!quarantine

Puts a user in quarantine: removes all their roles (they are saved so they can be restored later) and isolates them with a timeout. Quarantine is reverted with !unquarantine or expires on its own — after 7 days by default. Usage: !quarantine <@user> [duration] [reason] Aliases: cuarentena Permissions: Moderate Members (or a moderation role authorized in Lucie) The duration is optional and accepts formats like 45s, 10m, 1h, 3d or 1w. Without a duration, 7 days apply. Examples
Lucie needs the Manage Roles and Moderate Members permissions to apply the quarantine. Besides this manual command, automatic protections (such as anti-raid) can also quarantine users based on your configuration.

​
!unquarantine

Lifts a user’s quarantine: gives back the roles that were saved and removes the isolation. Usage: !unquarantine <@user> [reason] Aliases: uncuarentena, quitarcuarentena Permissions: Moderate Members (or a moderation role authorized in Lucie) Examples

​
!banraid

The global anti-raid ban. When used against a raider, Lucie bans them from your server on the spot (with their case and modlog entry, like a normal ban) and sends the case to the Lucie team along with any evidence you attach. If the team verifies the raid, the user is banned from every server Lucie is in — and if they join a new server, the ban re-applies on its own. Usage: !banraid <@user|ID> [reason] Aliases: raidban, globalban Permissions: Ban Members (or a moderation role authorized in Lucie) Examples
Attach screenshots or videos to the same message as the command: they are validated and sent as evidence along with the report. Attachments of disallowed types are rejected.
!banraid list shows the global bans currently in force: user, reason, origin server and date. If any of them has been lifted on your server, it is indicated.
!banraid remove <ID> lifts the global ban only on your server; on the rest they remain banned. Lifting it across all servers is the Lucie team’s call.
!banraid check goes through the global ban list and bans anyone on it who is present in your server. Protected members (staff/immune) are respected, and you are informed of any failures.
!banraid report <ID> [reason] sends the case to the Lucie team without applying the local ban. If there is already a pending report for that user, you are notified. It also accepts attached evidence.
Only the Lucie team can turn a report into a global ban (and lift it from every server at once). Your !banraid always goes through that review: no one can ban globally on their own.

​
!unbanraid

Shortcut for !banraid remove: lifts a global anti-raid ban only on your server (on the others the user remains banned). Usage: !unbanraid <@user|ID> Aliases: unraidban Permissions: Ban Members (or a moderation role authorized in Lucie) Examples

​
!check

On-demand security diagnostics. It reviews at a glance:
  • Lucie’s role and permissions — whether her role is high enough and whether she has the 9 key moderation permissions (or Administrator).
  • Logging — whether the modlog is configured, exists, and Lucie can write to it.
  • Protections — what you have enabled and what’s missing: anti-raid, anti-nuke, anti-alts, antibots, anti webhook-spam, honeypot channel, AutoMod filters, warn escalation, and how many global anti-raid bans are in force.
Usage: !check Aliases: diagnostico, comprobar Permissions: Administrator or Manage Server (or being the server owner) Examples
Run it right after inviting Lucie and every time you reorganize roles or channels: it tells you exactly what to fix before it matters.

​
!verify

Manages the new-member verification panel. Verification is configured in the web dashboard (Anti-raid → Verification): there you choose the role that gets granted, the channel, and the mode (basic or captcha). This command (re)publishes the message with the verification button in the configured channel — for example, if the original message was deleted. Usage: !verify panel Aliases: verificacion, verification Permissions: Administrator or Manage Server (or being the server owner) Examples
If the panel isn’t published, Lucie tells you why: verification is disabled, no channel is configured, the channel no longer exists, or she can’t send messages in it.

​
Questions?

Configure everything from the web dashboard, invite Lucie if you don’t have her yet, or drop by the support server.