-
Notifications
You must be signed in to change notification settings - Fork 3
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
Warning system #94
Comments
A few clarifications needed, I think:
|
|
re 2. The record should maybe include who warned the user. While I hope that it won't matter in the context of where Cecil and Tim are currently deployed, if someone on staff ends up outing themselves as crap, it should be clear if someone's warn history includes entries from that person, so that it can be audited if necessary. Which leads to also: should it be possible for staff/admin to be able to strike someone's warning from their history if it comes to light that a warning was unjustified? |
That's what the "warner" part was meant to be. I was thinking that would be something like:
The phrasing was definitely unclear, I'll update it to match how I wrote it here. And I can absolutely make it a DeletableListView like the other ones I'm using in the new system. Should removing a warning take different permissions than adding one? |
Yeah. Like, if the warnings are allowed to be set by people with kick perms as well as ban perms, then they should only be removable by people with ban perms. And I know I said earlier that warning should be ban perms only, but upon reflection, allowing people with kick perms to be able to set warnings is probably good, but only allowing someone with ban perms to delete them would reduce abuse. |
Bitch eating crackers 😹 |
I'm integrating the warnlogs with the bans, kicks, and timeouts; what should the minimum permission be to view the whole discipline log? |
I'm torn between limiting it to those with ban perms, but being able to read the list when you are able to add to it doesn't seem out of order either. |
If those below ban can read it, it should be only ban or admin that can remove entries |
It would be cool to have a formalized warning system in the bot. Such as:
!warn @user reason
to give us somewhere to keep notes on people violating rules or being a problem.
It would also need a command like
!warn view @user
to see what their warn history is.The text was updated successfully, but these errors were encountered: