-
Notifications
You must be signed in to change notification settings - Fork 514
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
AntiBot configuration cannot be changed with /authme reload #896
Comments
It's hard to explain in English, I will explain it in French, sorry Sgdc. J'ai effectué des test et ça ne fonctionne pas très bien. J'ai rencontré plusieurs bug, et je ne peux pas tous les citer un-par-un. Tout ce que je peux te dire, c'est qu'au début de mes test ça avait l'air de fonctionner sauf pour J'en ai profité pour réfléchir à un système de configuration un peu plus différent qui pourrai remplacer celui actuel si jamais vous n'arrivez pas à résoudre les soucis.
Edit: J'ai encore testé, cette fois ci l'antibot s'est bien activé mais lorsque j'ai changé la sensibilité ça a cessé de fonctionner. |
@Twonox Could you try again? |
Quick translation of @Twonox's message is that Antibot doesn't seem to work well upon reloading. It's important to know that Antibot takes 90 seconds before it actually starts; you can check this with @sgdc3 fixed another bug with the commit just above, so if we could ask you to verify again @Twonox with that in mind. I create an issue for configuring the waiting period on startup in the meantime. |
Okay I will do some test tomorrow. |
It works perfectly, thanks ! :) |
When we change value of
enableAntiBot
then reload authme, the value isn't applied. We must reboot the server (or reload?).antiBotSensibility
does not work, we can't change sensibility.The text was updated successfully, but these errors were encountered: