-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Block some commands outside of #bot OR Make trup react #bot in case command is not used in #bot #10
Comments
In my opinion that would be annoying sometimes, for instance when it's important in the discussion. (E.g. it is about how long members have been on the server, "random guy> hey @ randommembername what's your favourite editor? randommembername> !fetch") Maybe instead post it in #bot-channel and then send a link to it? Although that too would suck if it's important in the currently discussed topic. |
!fetch specifically wouldn't be a command that would "enforce" being used in #bot. !setfetch for example, would be. |
Info is one of those things that should be the first priority to block usage of outside of #bot, due how big the response is. So would a flow of:
Be good here? |
yea, something like that. I'd not necessarily delete the users message, but have the bot just respond with "please ask in #bot" or sth... although deleting the message after a short time might be a good idea - should be discussed. The highest priority here imo is !setfetch tho, as there are still cases where !info could be part of normal conversation - whereas !setfetch really can't. |
by 6gk: unixporn/trup#131
Of course this should ignore moderators & the moderator category.
Commands like
Don't really have a place outside of #bot.
by Pan00Pernicek: unixporn/trup#148
just like this, it can be good idea to tell people to go to #bot instead with this reaction
The text was updated successfully, but these errors were encountered: