Skip to main content
Someone deleted a message right when you were about to read it? Lucie’s system recovers what just vanished from the channel: deleted messages, edits, and removed reactions. Everything lives in memory only, expires after 2 hours, and never touches the disk.

​
Why Lucie’s snipe is different

Most bots rely on Discord’s message : if the message was no longer cached when it got deleted, there’s no snipe. Lucie keeps her own lightweight of recent messages, so snipes cover the full 2 hours.
When moderation purges messages in bulk, those messages never generate snipes. What a moderator cleans up stays cleaned up.

​
Button navigation

The three lookup commands reply with a navigable embed:
  • ◀ ▶ — move between records without re-running the command. Only the person who ran the command can navigate; the buttons deactivate after 2 minutes.
  • ✖️ — dismisses the reply.
  • The optional [index] opens a specific record directly: 1 is the most recent.
Any Discord invite inside the content is shown as [invitación filtrada] (filtered invite).

​
!snipe

Recovers the channel’s most recently deleted messages: text, attachments (with a preview if it’s an image), stickers and, if it was a reply, who it was replying to plus an excerpt of that message. The embed shows when it was sent and when it was deleted. Usage: !snipe [index] Aliases: sn, snip Examples

​
!editsnipe

Shows the channel’s latest edits with the Before and After text, plus a link to jump to the edited message. Usage: !editsnipe [index] Aliases: esnipe, esn Examples
Only edits that change the text are recorded. If the only thing that changed was an embed (for example, a link preview loading in), it doesn’t count as an edit.

​
!reactionsnipe

Shows the latest reactions removed in the channel: who removed which emoji, which message it was on (with a direct link) and, if it’s a custom emoji, its image as a thumbnail. Usage: !reactionsnipe [index] Aliases: rsnipe, rs Examples

​
!clearsnipe

Clears the channel’s snipe records, with two scopes:
  • !clearsnipe (no arguments): deletes only your own trail — your deleted messages, your edits, and your removed reactions. Anyone can clear their own, no permissions needed. Anything you send from that point on becomes snipeable again.
  • !clearsnipe all: deletes all of the channel’s records (deletions, edits, and reactions). Requires the Manage Messages permission.
Lucie confirms how many records she cleared and her reply deletes itself after one second: clearing your trail shouldn’t leave a trail that you cleared it. For the same reason, the !clearsnipe message itself is never snipeable, even if you delete it by hand. Only works in servers. Usage: !clearsnipe [all] Aliases: clearsnipes, cs Examples
Letting anyone erase their own trail is deliberate: your messages are yours. Most bots only let moderators clear the snipe — or don’t allow clearing it at all.

​
Frequently asked questions

Possible causes:
  • More than 2 hours have passed since it was deleted: the record has already expired.
  • It was removed by a moderation purge: purged content is never recoverable, by design.
  • The author was a bot: bot messages are ignored.
  • The message had nothing to show: with no text, attachments, or stickers (for example, a message that only contained an embed), it isn’t recorded.
Anyone can erase their own trail with !clearsnipe (no permissions). To wipe the entire channel you need !clearsnipe all and the Manage Messages permission. The lookup commands (!snipe, !editsnipe, !reactionsnipe) don’t require any special permissions.
Each record expires exactly 2 hours after it happens, and each channel keeps at most the 25 most recent records of each type. Everything lives only in Lucie’s memory — nothing is written to disk — so if the bot restarts, the records disappear too. If you need them gone sooner, use !clearsnipe.
Questions, or something that doesn’t add up? Drop by the support server or review your settings in the web dashboard.