Quote:
Originally Posted by jpwanabe
I should of pointed this out before, but I solved my problem with the old version ecca.
sm_sleuth_bansallowed is set to 0 by default. Which means when some one has NO bans active but has been banned before, it will reban them. Setting this to 1 solved my problem. There was nothing wrong with the plugin, just my understanding of it.
One thing that I suggest you add. Make the ban reason say "[SourceSleuth] Duplicate account of XXXXX" or, if possible, add in the comments a link to the first account banned with that ip.
|
Thanks, this seemed to be the case with me as well. I could not get the duplicate account ban to properly trigger using the 1.3.0 fix version, but it works fine with 1.2.0 when sm_sleuth_bansallowed != 0, even after the ban has expired. edit: As a sidenote, I used the 1.3.0 fix for about 4 months. Got no errors whatsoever, but when I actually tried logging in with a duplicate account myself, it didn't trigger a ban (with 1.2.0 it does).