Closed calebj closed 7 years ago
As I see in user_allowed
this might cause issues to self bots (although they really should not use this cog). Closing, I doubt this simple check has any meaningful impact on performances anyway
Noooooo~
*screaming intensifies
I prevented selfbot-triggering with https://github.com/calebj/Red-DiscordBot/blob/selfbot/red_self.py#L173, and it's reliable. Only the user would be able to trigger their selfbot.
Would be neater if it had the option to edit or delete the original message in this case, too.
I wanted a toggle on trigger for selfbot. I sometimes want it to trigger on other user messages
I sometimes want it to trigger on other user messages
Er, no. That's against Discord ToS for userbots, and I won't support it. Feel free to write it yourself, though.
Then I assume you wil be removing your status(away) cog from selfbot distribution since it was basically similar
What distribution again?
If i am not mistaken. Cloning the selfbot from your fork (branch selfbot) comes with a cog called status (for away status)
It does not, and never did. Check for yourself.
God. I am mixing something up. My apologies
bot.user_allowed(message)
already does this