-
Notifications
You must be signed in to change notification settings - Fork 602
[Suggestion] log deleted messages feature #354
Comments
In addition, the ability to use the "Log History" command in a different channel would be a godsend. If I wanna read deleted messages I would love to be able to pop that lo into my own server or at least into the bot commands channel of the server in question, so as to not clog general (or wherever). |
@TotalLegitREMIX You can with command redirection. |
@LyricLy Could you please elaborate? That is in the section of "I know what I'm doing" and I am about at the "I know some of what I am doing". I input that command into the channel I want, and it gives confirmation "Successfully redirected STDOUT and STDERR to the current channel!" but then nothing gets redirected to that channel. No command responses in the same server or a different server end up there. I tried using "redirect [command]" to test if that does anything, but I still get the same results. Thanks for any and all help! |
@Lingrah Not the redirect command, the I believe undocumented command redirection feature. |
Okay well this kinda worked, if you need any additional information about this to help resolve this please let me know. First, after some commands it works correctly, but then also throws an error. So the commands work but it ALSO throws an error, If I run a channel relevant command like When attempting to quote something from channel A, back to that channel A, while running the command in channel B, I get the following error. Lately a 2 parter channel reliant command, like So as a tl;dr, the redirect command works sometimes, but not in the way you intended most of the time. |
The issue is that when you redirect, it can't find the original command message, so anything trying to affect that will raise an error. I may look into fixing this. |
@LyricLy yeah, we can redirect the command, but this will still notify people for example in a DM. |
An additional feature to Keyword Logger that logs deleted messages in enabled servers and send them in the same way the keyword logger would do (webhook/private dm)
The text was updated successfully, but these errors were encountered: