Incident replay
Build a post-mortem timeline of what happened in your community with a single command.
Build a report
Run n!incident <timeframe> [title] in your server, for example n!incident 2h raid from #general. You can also generate a report from the Incidents page in the dashboard. Use n!incidents to list your stored reports.
What the timeline captures
The report merges member joins and leaves, bans and unbans, moderation cases, automod hits, message deletions, channel or role changes and pings of @everyone, @here or a role into one timestamped timeline. It also flags message spikes: channels that suddenly move far above their normal rate.
Reading the deleted messages
Expand a deletion in the timeline to see the message that was removed, plus the messages around it in that channel. Bulk deletes and purges show a sample of what went with them - the bot records up to 20 messages per purge - along with how many were deleted in total and how many people they came from.
Activity retention
Reports are built from the last 14 days of recorded activity. Older events can no longer be replayed, so generate a report soon after an incident if you want the full picture. Message content inside a report is kept for 7 days, matching how long deleted messages are stored; after that the timeline still shows who deleted what and where, just not the text.
The Incidents pages
Every report is a stored snapshot with a shareable dashboard link. Open one and you get a chart of activity over time that you can drag across to look at one stretch, the kinds of event with their counts, and the timeline itself. A raid folds into runs such as 62 people joined that open with a click, every name is a shortcut to that person's events, and the search box finds people, channels and text. Filters are kept in the link, so you can send a filtered view to your team, or copy a plain-text summary. The timeline reads oldest first by default, with the window start and end marked; use the order switch to flip it.
Pings of @everyone and roles
Messages that used @everyone, @here or a role mention show up as Pings, with who sent them and where, and the side list shows which roles were pinged the most. They are found from the message text, so a ping from someone without permission to use it still appears, even though it notified nobody. The report keeps only the fact of the ping, not the message: open a ping to read the message while the bot still stores it (7 days), or see it with the deletion if it was removed afterwards.