aboutsummaryrefslogtreecommitdiff
path: root/docs/api.rst
diff options
context:
space:
mode:
authorRapptz <[email protected]>2016-08-14 13:41:57 -0400
committerRapptz <[email protected]>2016-08-14 13:42:39 -0400
commit83c7ba612edb8c1e5812688025d8e8fd5ddb5df6 (patch)
tree72009aa01c0ede5f03289cf7132ac72bd0e8735e /docs/api.rst
parent[commands] Delete module when it does not have a setup function. (diff)
downloaddiscord.py-83c7ba612edb8c1e5812688025d8e8fd5ddb5df6.tar.xz
discord.py-83c7ba612edb8c1e5812688025d8e8fd5ddb5df6.zip
Explain cases where the on_message_edit event can be triggered.
Diffstat (limited to 'docs/api.rst')
-rw-r--r--docs/api.rst26
1 files changed, 21 insertions, 5 deletions
diff --git a/docs/api.rst b/docs/api.rst
index 1e2b82cd..b9f39b0e 100644
--- a/docs/api.rst
+++ b/docs/api.rst
@@ -180,14 +180,30 @@ to handle it, which defaults to print a traceback and ignore the exception.
message or ``str`` to denote a regular text message.
.. function:: on_message_delete(message)
- on_message_edit(before, after)
- Called when a message is deleted or edited from any given server. If the message is not found in the
- :attr:`Client.messages` cache, then these events will not be called. This happens if the message
- is too old or the client is participating in high traffic servers. To fix this, increase
- the ``max_messages`` option of :class:`Client`.
+ Called when a message is deleted. If the message is not found in the
+ :attr:`Client.messages` cache, then these events will not be called. This
+ happens if the message is too old or the client is participating in high
+ traffic servers. To fix this, increase the ``max_messages`` option of
+ :class:`Client`.
:param message: A :class:`Message` of the deleted message.
+
+.. function:: on_message_edit(before, after)
+
+ Called when a message receives an update event. If the message is not found
+ in the :attr:`Client.messages` cache, then these events will not be called.
+ This happens if the message is too old or the client is participating in high
+ traffic servers. To fix this, increase the ``max_messages`` option of :class:`Client`.
+
+ The following non-exhaustive cases trigger this event:
+
+ - A message has been pinned or unpinned.
+ - The message content has been changed.
+ - The message has received an embed.
+ - For performance reasons, the embed server does not do this in a "consistent" manner.
+ - A call message has received an update to its participants or ending time.
+
:param before: A :class:`Message` of the previous version of the message.
:param after: A :class:`Message` of the current version of the message.