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

Warning system #94

Open
diziara opened this issue Jan 1, 2021 · 9 comments
Open

Warning system #94

diziara opened this issue Jan 1, 2021 · 9 comments
Labels
enhancement New feature or request

Comments

@diziara
Copy link
Collaborator

diziara commented Jan 1, 2021

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.

@TurqW
Copy link
Owner

TurqW commented Jan 2, 2021

A few clarifications needed, I think:

  1. Permissions: Can I just make it "anyone that has the 'kick members' permission can warn people? Or do I need to configure a role per server?
  2. What should the warning history look like? Just a list of [Date]: warned by [warner] for [reason]?
  3. Should warnings be visible at all on servers where they weren't received? Should off-server warnings in the history be shown with some sort of flag on them, or maybe just a and 3 other off-server warnings at the end?

@TurqW TurqW changed the title Waring system Warning system Jan 2, 2021
@diziara
Copy link
Collaborator Author

diziara commented Jan 2, 2021

  1. I think it should be able to ban, but if it's not crazy, a setting to choose between kick or ban might be a good idea.
  2. Yeah, it doesn't need to be complicated
  3. I'm of mixed thoughts. Maybe a config for if the admin wants to share and/or see other servers data?

@diziara diziara added the enhancement New feature or request label Dec 30, 2021
@diziara
Copy link
Collaborator Author

diziara commented Jan 8, 2022

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?

@TurqW
Copy link
Owner

TurqW commented Jan 8, 2022

That's what the "warner" part was meant to be. I was thinking that would be something like:

/warnlog <user>

Warnings received by <user>
2021/01/22: warned by Death Kitten for loud chewing
2021/03/14: warned by Tin Wizard for insulting robots
And 3 public warnings on other servers, most recent on 2022/01/07

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?

@diziara
Copy link
Collaborator Author

diziara commented Jan 9, 2022

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.

@diziara
Copy link
Collaborator Author

diziara commented Jan 9, 2022

2021/01/22: warned by Death Kitten for loud chewing

Bitch eating crackers 😹

@TurqW
Copy link
Owner

TurqW commented Jan 17, 2022

I'm integrating the warnlogs with the bans, kicks, and timeouts; what should the minimum permission be to view the whole discipline log?

@diziara
Copy link
Collaborator Author

diziara commented Jan 17, 2022

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.

@diziara
Copy link
Collaborator Author

diziara commented Jan 17, 2022

If those below ban can read it, it should be only ban or admin that can remove entries

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants