- #Spam bot for discord servers how to#
- #Spam bot for discord servers manual#
- #Spam bot for discord servers verification#
#Spam bot for discord servers manual#
A manual silence can also be configured to expire after a set period of time. However, some server admins are lazy, so an automatic expiration can be added. By default, silences that happen automatically are never rescinded until a moderator manually unsilences someone. If they trigger the anti-spam, or a moderator uses the !silence command, they will have the role added, any messages sent in the last 5 seconds (by default) will be deleted, and they'll be restricted to speaking in #Silence Containment. Under normal operation, when a new member joins the server, they are automatically given (and if it's been enabled) and are immediately allowed to speak. The bot has two distinct modes of operation. What this role actually does is up to the administrators - usually it simply disables sharing images or embeds. However, to help compensate for this, the bot can also be configured to add a temporary role to newer users that expires after a configurable amount of time.
#Spam bot for discord servers verification#
The role being added can also short-circuit Discord's own verification rules, which is an unfortunate consequence, but in practice it usually isn't a problem. Some admins do not like this approach because they prefer to personally audit every new member, but this is not viable for larger servers. This is essentially an automated airlock that only engages if the bot detects a raid, instead of forcing all new members to go through the airlock. This architecture was chosen to allow the bot to survive a mega-raid, so that even if 500+ bot accounts storm the server all at once, if the bot goes down or is rate-limited, they can't do anything because they haven't been given the role, and so the server is protected by default. Most servers make it so #Raid Containment is only visible to anyone without the role, ensure #Silence Containment is only visible to anyone with the role, and hide #Log Channel from everyone except admins. The admins of the server can configure the visibility of the containment channels. This ensures that, no matter what new roles might be added in the future, will always prevent you from sending messages on any channel other than #Silence Containment. Then, it creates the role by adding permission overrides to every single channel on the server that prevent you from sending messages on that channel, except for the #Silence Containment channel. It then removes all permissions from but adds an override for #Raid Containment so that anyone without the role can only speak in #Raid Containment. It adds all these permissions to the role, then goes through all existing users and adds the role to them. Roles first-time setup is run on a server, the bot queries and stores all the permissions given to the role. My moderation architecture goes like this: Many anti-spam solutions lock down the server by forcing new members to go through an airlock channel, but I consider this overkill and the result of poor anti-spam bots that are bad at actually stopping trolls or responding to raids. There are disagreements over exactly how an anti-spam bot should work, with a wide-range of preferred behaviors that differ between servers, depending on the community, size of the server, rate of growth of the server, and the administrators personal preferences.
#Spam bot for discord servers how to#
This post is an effort to educate all the other anti-spam bots on how to ascend beyond a simple “mute someone if they send more than N messages in M seconds” filter and hopefully make better anti-spam bots so I don't have to. I am no longer maintaining this bot beyond simple bugfixes because I have better things to do with my time, and I'm tired of people trying to use it because “it's the best anti-spam bot” even after I deprecated it. My friends and I were determined to keep our discord server public, so I went about creating the first anti-spam bot for Discord. Back when Discord was a wee little chat platform with no rate limiting whatsoever, it's API had already been reverse-engineered by a bunch of bot developers who then went around spamming random servers with so many messages it would crash the client.
0 kommentar(er)
