Stop the deletion-log loop
Pup skips edit and deletion events for posts in every configured log destination. When retention removes old log posts, those removals no longer create another round of deletion logs. Try it: Let retention clear a log post, then check that it does not create a new entry in the message log.See the message Pup recently saw
For new messages covered by an enabled edit or deletion route, Pup temporarily records the text and author. If Discord later sends a partial event, the log can use that recent record to show the earlier text and identify the author. The message-content window is configurable from 1 to 168 hours and defaults to 24 hours. A message Pup did not see, or one whose temporary record has expired, can still show unavailable text. This update does not recover older message content. Try it: Edit and delete a newly observed message, then compare the entries in the message log.Read member changes and case identities
Member logs show the recorded member name and before and after values for the name and avatar changes Discord supplies. Role changes list added and removed roles separately. An old avatar link can stop working after Discord removes that image. Moderation cases keep the identity recorded when the case was created, even if the member later leaves or is banned. Pup labels it as recorded information. Some older cases stored only a Discord ID; those cases still show the ID because a past name cannot be recovered from it. Try it: Check a recent member name, avatar or role change in the member log. Open a banned member’s case and compare the recorded identity with its Discord ID.For self-hosted installs
Migration0141_logged_message_snapshots adds the temporary message record used by edit and deletion logs. Take and verify a database backup before applying this forward-only migration. The existing message-content retention setting controls how long new records remain available.