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

[V3] Report Feature #1280

Closed
2 of 3 tasks
mikeshardmind opened this issue Jan 29, 2018 · 1 comment
Closed
2 of 3 tasks

[V3] Report Feature #1280

mikeshardmind opened this issue Jan 29, 2018 · 1 comment

Comments

@mikeshardmind
Copy link
Contributor

Type:

  • Suggestion
  • Bug
  • Enhancement

If this belongs in core red, I can port my ReportTool cog and make a corresponding PR to have it be a core part of Red. If it is decided it doesn't, I will continue to maintain a v3 compatible cog anyway.

Cog would be usable from server or DM, if DM, it would prompt for server based on shared servers. If only 1 shared server, this prompt would be skipped. Would get report data and dump it into a per-guild configurable channel. Report data would be gathered in DM only, uses of the command outside of DM would result in a switch to DM and a removal of the invoking message.

Additionally, it would allow for moderator responses to reports from the bot. (this is not implemented in the existing v2 cog currently)

For reference, here is the cog as it exists for v2

@mikeshardmind
Copy link
Contributor Author

Closing this now that report is in

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

2 participants