Kr1S-D
commented
2 months ago 1-2-3) ok, will be implemented in the next version
4) Checks of this type can create many false positives, there is already a system that counts if the names are similar to each other or something else but it has been deactivated as it creates too many false positives, furthermore in addition to the regexes you can also add strings that the code must contain for the nickname to be blocked.
There are no algorithms that evaluate whether there are randomly generated strings, there are literally names where there are no vowels, consonants, which have numbers in the center which could be false positives
As for understanding how regexes work, there are sites capable of generating them, even chatgpt can help
Statistics of how many requests have been made in a given period (nice thing if the server decides it would like to pay for a premium service like proxycheck.io)
For more description of when the message is executed, see the messages.yml file. This will improve the understanding of the translator.
such as onping, analyzer or kick messages (antibotmode, ping, timer vs wait)
Simplify the blocking of players' nicknames. Instead of using regex etc, make it so that if a word appears in a nick, either in upper/lower case or random letters, it gets blocked automatically. Enough users may not understand how regex works properly and how to write it in a way that the plugin will understand.