-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
[SUGGESTION] Add a lock command #116
Comments
This technically exists but is locked down since it hasn't been tested enough yet. If you give me a server id I can enable it there for you. Any bugs you find with it can be dropped in the #fire-help channel in the Fire Discord or here |
Awesome, thanks. I will report any bugs I come across. My server ID is 838060894759682118. |
The |
You only added in the ID through an edit so when I saw that comment, it wasn't there. I've gone ahead and enabled it but the slash command may not show up just yet. You should be able to use |
No problem thanks. |
Does fire have a command to lock a single channel instead of all channels? |
No it does not |
Then I think we can go back to my original comment. I think this would be a good addition to Fire. |
Describe the solution you'd like
A lock command that disallows the permission for the @everyone role to send messages in the invocation channel.
The text was updated successfully, but these errors were encountered: