An intent is a type of listener or something that lets a Discord application watch and track things such as messages, members and activeness. Intents need to be manually verified by the company Discord. In this page, the intents that we use will be explained as what they do, why we need them and how they'll be used including data, storage and security of potentially sensitive information (if stored at all).
Embedded Files
⚠️
This may not look correct on a mobile device or in a portrait orientation. Please enable desktop mode if on mobile to visualize the below correctly.
Intents available from Discord
Text formatted with strikethrough are not used by ERSMS.
Server Members
Presence
Message Content
The server members intent lets the ERSMS application have access to all members in the guild where its located. This includes usernames, nicknames, roles and join dates. The bot has access to the Discord ID of (a) user(s), username, discriminator (#0000 for example) and their global name / nickname. Roles, server join dates, user flags, premium status (boosting info), avatar, banners and more are also accessible. Without this intent, applications only have access to users who directly interacted with the bot (via command interaction) or directly mentioned in an event (such as someone joining or leaving).
This intent allows applications to receive and process presence updates for users in servers. This includes data about users being offline / online, access to their custom status, when someone changes their presence (eg. Online to Idle). In short, this presence allows the bot to know what each user is doing such as games or when they're online / what they're actively doing. Bots have automatic events when something changes from the events above. This intent is mostly useless to bots that don't track users.
Applications with this intent can read / process all message content sent in the guild. This includes attachments, messages, embeds and events such as editing a message or removal of a message. Without this intent, applications only have access to message objects which includes the ID of the message, attachments, mentions of users, roles and channels when a message is delivered into a guild (a Discord server where ERSMS is located).
Why does ERSMS require / need these intents?
Server Members
This intent is required for welcome messages, user leave logs, boost events and more. ERSMS requires these intents when a user enables welcome messages for members who join. For example, when a user joins, an event is called and ERSMS looks in the database if the welcome module has been enabled. If it has been configured, the application "ERSMS" will send an embed / raw message to welcome the user in a certain channel. This would not work without the event, therefore needing the intent. Furthermore, guild boost events also require this as if there's a boost role configuration, the application needs to automatically hand out roles immediately without a command, so once again, ERSMS uses this intent for this event. For security purposes, a guild owner might also require leave logs or want roles that come back after joining, so ERSMS needs access to roles that users have on leave to be able to re-add those roles to the user on-join if a guild manager wants so. For example, this may be used in blacklists where users cannot apply for staff roles etc, where normally a user could just leave and rejoin to remove roles.
Message Content
Guild managers can set message restrictions / events such as blacklisted words. Managers may want to restrict profanity words such as "fuck", "shit" or slurs including but not limited to racial ones or other hate speech. Yes, guild moderators may use the provided "block word event" in community guilds but customizability is very limited. With ERSMS, you will be able to block similar words automatically or instead of just blocking the whole message altogether, the guild moderators may set ERSMS to log words or add a point system to users, where if you reach a certain amount of points, you'll get moderated based on the configuration set by moderators. ERSMS also uses this intent for message logging for servers. Popular logging bots use this intent to log messages. ERSMS will also implement this system where message edits or removals will be logged in set channels. ERSMS will require these intents to log such events and add more customizability to message content (restriction of lengths, character count or emoji counts etc).
Google Sites
Report abuse