User Spam
What it is for
Section titled “What it is for”User Spam reacts when one member floods a channel with messages. It is useful against pasted message bursts, key-smashing, compromised accounts, and users trying to make a conversation unreadable.
This feature counts message frequency; the messages do not need to contain the same text. Use Cross-Posting when the problem is one person repeating the same message across several channels.
Open Auto-Mod → Archivian Auto-Mod → User Spam in your server’s dashboard.
How it works
Section titled “How it works”Archivian counts messages sent by the same member in the same channel during the configured time window. When the count reaches the threshold, it gathers the messages involved and runs the configured actions. A short settling period may include additional messages from the same burst.
Messages from users Archivian recognizes as server staff are not checked. New messages are what contribute to the rate counter; editing a message does not create another message in the burst.
Threshold settings
Section titled “Threshold settings”Messages
Section titled “Messages”The threshold is how many messages one member must send before the feature triggers. The dashboard allows 2–20 messages.
Lower values react sooner but can catch enthusiastic members sending several legitimate messages. Higher values tolerate more activity before acting.
Window
Section titled “Window”The window is how many seconds those messages may span. The dashboard allows 1–60 seconds.
A longer window makes the feature more sensitive because members have more time to reach the threshold. A shorter window focuses on rapid bursts.
The default is 20 messages within 10 seconds. Keep that as a safe first test for active communities. For a slower support server, something like 8 messages within 5 seconds may be appropriate after reviewing normal member behavior.
Exceptions
Section titled “Exceptions”- Ignored Channels exempts selected channels.
- Ignored Categories exempts channels in selected categories.
- Ignored Roles exempts any member who has at least one selected role.
Consider exempting bot-command or counting-game channels if rapid member messages are normal there. Do not exempt broad public categories unless necessary.
Actions
Section titled “Actions”- Action Reason is used in alerts, audit logs, and cases. For example:
Sent too many messages too quickly. - Delete Messages removes the messages that contributed to the spam detection.
- Add Roles assigns selected roles, such as a restricted-access role.
- Remove Roles removes selected roles.
- Create a Case records a note or warning, or applies a timeout, kick, or ban. Timeout and ban actions include duration controls; bans can also purge recent messages.
- Send a Message can send up to four configurable messages to the affected channel, the member’s DMs, or another channel. Placeholders can include the member, message count, affected channels, and message links.
Start with deletion and a short DM explaining the rate limit. A brief timeout is useful for repeated or clearly intentional flooding, but a ban is rarely a suitable first response to message frequency alone.
Tuning
Section titled “Tuning”If normal conversations trigger the feature, raise the message threshold or shorten the window. If obvious floods get through, lower the threshold or lengthen the window. Change one value at a time so you can tell which adjustment helped.