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: Add within timeframe to warningActions #982

Closed
TomLewis opened this issue Mar 1, 2023 · 0 comments · Fixed by #995
Closed

Suggestion: Add within timeframe to warningActions #982

TomLewis opened this issue Mar 1, 2023 · 0 comments · Fixed by #995

Comments

@TomLewis
Copy link
Contributor

TomLewis commented Mar 1, 2023

We have this issue where we cant use warningActions as a 10+ year old server, we have players that got warnings years ago but are basically differnt people now, 10 years is a long time!

We would like to be able to use warningActions if the warnings are given within a timeframe, say if you get 3 warnings in 1 week, then you get a temp ban etc, or if you get 3 warnings in one day then you get a perm ban etc etc.

Not those exact examples, but being able to set a timeframe for automated warnings would be very, very handy, the problem is if a player has accuilated 20+ warnings over 10 years, and we implemenet this, they will get punished for basically doing nothing as their warnings were from a long period ago or not recent.

Expanding this https://banmanagement.com/docs/banmanager/configuration/config-yml#warningactions

confuser added a commit that referenced this issue Sep 8, 2024
this enables triggering commands only if the total accumulated points within the timeframe is reached

e.g. for a point value of 5, setting the timeframe to 30d will mean the command will only be executed if within the last 30 days the total number of points reached by the player is also 5

fixes #982
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants