Update intents for message intent becoming privileged

Author: BobDotCom

discord/flags.py

@@ -546,11 +546,12 @@ def none(cls: Type[Intents]) -> Intents:
     @classmethod
     def default(cls: Type[Intents]) -> Intents:
         """A factory method that creates a :class:`Intents` with everything enabled
-        except :attr:`presences` and :attr:`members`.
+        except :attr:`presences`, :attr:`members`, and :attr:`guild_messages`.
         """
         self = cls.all()
         self.presences = False
         self.members = False
+        self.guild_messages = False
         return self
 
     @flag_value
@@ -767,6 +768,13 @@ def messages(self):
         - :func:`on_reaction_add` (both guilds and DMs)
         - :func:`on_reaction_remove` (both guilds and DMs)
         - :func:`on_reaction_clear` (both guilds and DMs)
+
+        Since this includes :attr:`guild_messages`, this intent is privileged. For more information go to the :ref:`message intent documentation <need_message_intent>`.
+
+        .. note::
+
+            Currently, this requires opting in explicitly via the developer portal as well.
+            Bots in over 100 guilds will need to apply to Discord for verification.
         """
         return (1 << 9) | (1 << 12)
 
@@ -794,6 +802,13 @@ def guild_messages(self):
         - :func:`on_reaction_add` (only for guilds)
         - :func:`on_reaction_remove` (only for guilds)
         - :func:`on_reaction_clear` (only for guilds)
+
+        For more information go to the :ref:`message intent documentation <need_message_intent>`.
+
+        .. note::
+
+            Currently, this requires opting in explicitly via the developer portal as well.
+            Bots in over 100 guilds will need to apply to Discord for verification.
         """
         return 1 << 9
 

docs/intents.rst

@@ -11,7 +11,7 @@ In version 1.5 comes the introduction of :class:`Intents`. This is a radical cha
 
 These intents are passed to the constructor of :class:`Client` or its subclasses (:class:`AutoShardedClient`, :class:`~.AutoShardedBot`, :class:`~.Bot`) with the ``intents`` argument.
 
-If intents are not passed, then the library defaults to every intent being enabled except the privileged intents, currently :attr:`Intents.members` and :attr:`Intents.presences`.
+If intents are not passed, then the library defaults to every intent being enabled except the privileged intents, currently :attr:`Intents.members`, :attr:`Intents.presences`, and :attr:`Intents.guild_messages`.
 
 What intents are needed?
 --------------------------
@@ -34,7 +34,7 @@ For example, if you want a bot that functions without spammy events like presenc
     # from discord.ext import commands
     # bot = commands.Bot(command_prefix='!', intents=intents)
 
-Note that this doesn't enable :attr:`Intents.members` since it's a privileged intent.
+Note that this doesn't enable :attr:`Intents.members` or :attr:`Intents.guild_messages` since they are privileged intents.
 
 Another example showing a bot that only deals with messages and guild information:
 
@@ -76,7 +76,7 @@ A privileged intent is one that requires you to go to the developer portal and m
 
 .. warning::
 
-    Enabling privileged intents when your bot is in over 100 guilds requires going through `bot verification <https://support.discord.com/hc/en-us/articles/360040720412>`_. If your bot is already verified and you would like to enable a privileged intent you must go through `Discord support <https://dis.gd/contact>`_ and talk to them about it.
+    Enabling privileged intents when your bot is in over 100 guilds requires going through `bot verification <https://support.discord.com/hc/en-us/articles/360040720412>`_.
 
 .. note::
 
@@ -107,6 +107,19 @@ Member Intent
 - Whether you want to request the guild member list through :meth:`Guild.chunk` or :meth:`Guild.fetch_members`.
 - Whether you want high accuracy member cache under :attr:`Guild.members`.
 
+.. _need_message_intent:
+
+Message Intent
+++++++++++++++++
+
+- Whether you have a message based command system using ext.commands
+- Whether you use the :func:`on_message` event for anything, such as auto-moderation.
+- Whether you track message edits or deletions using :func:`on_message_edit`, :func:`on_message_delete`, :func:`on_raw_message_edit`, :func:`on_raw_message_delete`.
+- Whether you use any reaction related events, such as :func:`on_reaction_add`, :func:`on_reaction_remove`, and :func:`on_reaction_clear`
+
+.. note::
+    This only applies to :attr:`Intents.guild_messages`, not :attr:`Intents.dm_messages`. The bot can still recieve messages in DMs and when mentioned.
+
 .. _intents_member_cache:
 
 Member Cache