Implement Message context menu & command for discord.py's "No General" role usage. #175
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
LeoCx1000
reviewed
Aug 5, 2024
Co-authored-by: Leonardo <leonardocavenago05@gmail.com>
AbstractUmbra
changed the title
Soheab
approved these changes
Aug 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed by the moderation team, I have implemented the necessary machinery to achieve the following flow:
Context Menu on user message -> Prompt mod/helper for thread title -> create help forum thread based on input and message content and optionally apply a timed "No General" role on the target author (default is to do so).
The prefix command works the exact same as
?tempblockand no "permanent" variant exists.This is currently open to moderators and discord.py helpers, but easily changed if needed.
I have done my best to replicate the discord.py server infrastructure involved in this PR, as well as the relevant RDanny mechanisms involved and all seem to work a-ok now:-
