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

Automatically detect punishment evasion #11

Open
TBG1000 opened this issue Jul 6, 2022 · 0 comments
Open

Automatically detect punishment evasion #11

TBG1000 opened this issue Jul 6, 2022 · 0 comments

Comments

@TBG1000
Copy link
Member

TBG1000 commented Jul 6, 2022

Issue:

Alternate accounts or new users have to be manually checked out by staff to figure out if they may be evading an active punishment. For this reason, an evading user may go unnoticed for a considerable amount of time unpunished.

Background / pre-existing solutions:

Back on TGM, a solution in WarzoneMC/tgm#668 was developed but never merged due to API overload concerns. The proposed changes checked the alternate accounts of a user when joining and notified staff members through the chat about potential punishment evasion.

Desired solutions:

Similar to what was described above, the current punishment system should be able to check the alternate accounts of a user (if any) when they join, then shortly afterwards notify staff members about potential evasion should any of the alts have an active punishment.

Additionally, and if performance allows for it, staff members could also be notified about potential evasion when they join the server. Mars would look through the alts of all connected players and check if any of them may be evading. This functionality could also instead be encapsulated under a command (i.e /punevasion) so that multiple staff members joining do not send multiple requests to the API, causing issues.

Affected areas / files:

  • Punishment system
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant