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

Way for users to delete requested tag #3

Open
JavidPack opened this issue Apr 14, 2019 · 3 comments
Open

Way for users to delete requested tag #3

JavidPack opened this issue Apr 14, 2019 · 3 comments
Assignees

Comments

@JavidPack
Copy link
Contributor

It has been suggested that the user who requested a tag or search can trigger the tag to be deleted. The suggestion was to react to the message with X emoji. I was also thinking an .oops command could also undo a mod command.

This would require remembering a user to last requested message mapping.

@Metacinnabar
Copy link
Contributor

.oops deleting the message above would be very useful, especially for unglobal tags. Also, delete the .oops command after 2 seconds or something

@Agrair
Copy link
Contributor

Agrair commented Jan 19, 2020

I don't think the overhead would be that bad. Create a new ReplyAsync in BotModuleBase that calls the original ReplyAsync whilst indexing a static Dictionary<ulong, ulong>. The 'oops' command would have easy access to the dictionary. I don't think it even has to be concurrent.

@JavidPack JavidPack reopened this Sep 3, 2021
@Jofairden
Copy link
Member

I like the idea of an .oops command, it can definitely be made.
The easiest way to do this is just save the command output in a short lived cache, and allow up to 30 seconds for example to use it. However, nowadays discord also support buttons. Im not sure a privately seen button can be added to messages that are viewable by everyone, but it is worth looking into

@Jofairden Jofairden self-assigned this Jun 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants