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

Suggestion: Player Reports / Claims #388

Open
ChrisLenga opened this issue Jun 30, 2021 · 3 comments
Open

Suggestion: Player Reports / Claims #388

ChrisLenga opened this issue Jun 30, 2021 · 3 comments
Labels
enhancement New feature or request

Comments

@ChrisLenga
Copy link

So this may require some explanation, which I'll try to do to the best of my ability.

Player report ability will be critical so that players can report those breaking the rules to the admin team.

Another component to this is admin claiming and clearing of reports. One thing that is very much lacking is the ability to view any active reports, and claiming a report identifying that you are handling the admin sit.

Example: Player Bob reports Randy for RDM. There's a pending report yet to be handled by a staff member. Prior to a staff member teleporting to handle the sit, that staff member claims, whether via a button or automatically on teleport. Then that report turns into an "admin sit/in progress" in which no other staff is able to teleport to that incident.

Another phase of this would be an escalation during a sit, where say a "Moderator" lacks the permissions or cannot help a user that they showed up to a sit for, and needs to escalate to an "Admin" which allows a member of that role to teleport to the sit, thus bypassing the previous preventative.

Once done, any staff members involved in a said incident would write a brief note about what happened, and then close out the report. We require all of our staff here to file incident reports on all bans, for example.

This will go a long way, especially on bigger servers to preventing eight staff members from showing up to one incident, as then eight staff members are using an admin function, thus causing a drain of system resources to handle each of those requests. Something we struggle with as a bigger server that none of our admin or management panels is able to address.

@ChrisLenga
Copy link
Author

Additionally from a management perspective, a log somewhere of who goes to sits, and how many that user does, would also be extremely helpful. Something that an individual of a specific permission level can pull up individual staff members and see similar how we have hours played how many sits they've completed. Perhaps even a potential situation for an API straight off to Discord to a channel id we specify that accumulates said log for all sits handled, and any completed notes for sits completed.

@ChrisLenga
Copy link
Author

One thing to note about this function, there should be a mandatory cooldown that restricts a player from spamming a /report or /calladmin command. This doesn't entirely need to be a setting I don't think, but definitely should be put into place. I'd say probably a minute is a safe amount of time (cooldown) for an individual player to use the above commands.

Additional functionality, such as /report and under suggestion, shows something like /report {id} {reason} so that they know to report the id of a player, and the reason for the report.

@redacid95
Copy link

I would also suggest if an ID isn't passed in the command, that it collects the IDs of everyone in a decent sized area of the reporting player. That way we can get a potential list of players we may need to take action on.

@tabarra tabarra added the enhancement New feature or request label Jun 12, 2022
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

3 participants