Skip to content
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

Open
eepykate opened this issue Mar 2, 2021 · 4 comments
Labels
enhancement New feature or request Priority: Low

Comments

@eepykate
Copy link
Contributor

eepykate commented Mar 2, 2021

block some commands outside of #bot

by 6gk: unixporn/trup#131

Of course this should ignore moderators & the moderator category.

Commands like

  • role
  • info
  • desc
  • setfetch
  • help

Don't really have a place outside of #bot.


Make trup react #bot in case command is not used in #bot

by Pan00Pernicek: unixporn/trup#148

Screenshot_20210129_113430
just like this, it can be good idea to tell people to go to #bot instead with this reaction

Editor's note: discord uses :hash: for #, and the rest are regional indicators. Can be used to reduce spam.

@eepykate eepykate added the enhancement New feature or request label Mar 2, 2021
@eepykate eepykate changed the title make bot react #bot incase command is not used int #bot Make trup react #bot in case command is not used in #bot OR block some commands outside of #bot Mar 2, 2021
@eepykate eepykate changed the title Make trup react #bot in case command is not used in #bot OR block some commands outside of #bot Block some commands outside of #bot OR Make trup react #bot in case command is not used in #bot Mar 2, 2021
@legendofmiracles
Copy link
Contributor

legendofmiracles commented Mar 17, 2021

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.

@elkowar
Copy link
Contributor

elkowar commented Mar 19, 2021

!fetch specifically wouldn't be a command that would "enforce" being used in #bot. !setfetch for example, would be.

@davidv171
Copy link
Contributor

davidv171 commented Apr 3, 2021

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:

  1. user posts "illegal" command in #lounge
  2. user's message is deleted, he is summoned into #bot , with the response there

Be good here?

@elkowar
Copy link
Contributor

elkowar commented Apr 3, 2021

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.
Also this should not trigger in any of the mod-internal channels, where !info may be relevant.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Priority: Low
Projects
None yet
Development

No branches or pull requests

4 participants