-
-
Notifications
You must be signed in to change notification settings - Fork 89
Migrate other moderation commands #64
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
Comments
Naturally blocked by #59 |
I will add a kick command such as /kick @user |
Only |
We'll have to discuss whenever we still want the mute command. Discord just released time-outs Only issue is, UI allows upto 1 week. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Will make a prototype of the whois command ^^ |
This issue is stale because it has been open 30 days with no activity. Remove stale label, comment or add the valid label or this will be closed in 5 days. |
Next to the main moderation system (#63 ) we also have to migrate other important moderation commands, such as the mute, whois and modlogs system.
For reference, this is how it works as of today:
?whois <user>
by Dyno can be used to get an overview of a specific user. For example when he joined and registered.(implemented)?modlogs <user>
by Dyno shows all moderation actions that have been taken against an user.(implemented)>mute <user>
and>unmute <user>
by Inori Chan to mute or unmute an user.(implemented)?mute <user> <time> <message>
by Dyno to mute an user.<time>
and<message>
are optional.The text was updated successfully, but these errors were encountered: