ChrisLenga
commented
3 years ago 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.
redacid95
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.