[jpwanabe]

Ever get that fix done Ecca?

[ecca]

Yes , i'm working at the moment. Throw me a pm if you're interested of testing it.

[Blah91]

sm_sleuth_bantype <option> 0 - Ban all type of lengths, 1 - ban only permanent bans

Does not work either. I have set it to 1 and it re-bans players with short bans.

Bumping. Really need to know how to fix this ecca. Banned someone for mic spamming for 30 min, he came back the next day and it rebanned him. I don't want to uninstall this, it catches so many hacker alts.

Combined with this bug, this plugin is practically useless until fixed.

[ecca]

Try download this one: HERE

[Blah91]

Thanks for the update... but unfortunately now this plugin does not work at all

I tested this plugin by permabanning my friend's steamid, but with my own ip. SourceSleuth didn't ban me even though it should have (I think).

I'm using these settings:

sm_sleuth_bantype 1
sm_sleuth_actions 1

Plugin is loaded and running:

 52 "SourceSleuth" (1.3 fix) by ecca

sm plugins info 52
  Filename: SourceSleuth.smx
  Title: SourceSleuth (Useful for TF2 servers. Plugin will check for banned ips and ban the player.)
  Author: ecca
  Version: 1.3 fix
  URL: http://sourcemod.net
  Status: running
  Reloads: Map Change if Updated
  Timestamp: 09/12/2013 17:14:22
  Hash: d50f4a2e7216d832663a356b74d343ea

[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.

[Echo_can]

I have an issue where its banning a guy that has 4 bans but the last ban was a 30min ban

here is my cfg incase i did something wrong

// This file was auto-generated by SourceMod (v1.6.0-dev+4127)
// ConVars for plugin "SourceSleuth.smx"


// Sleuth Ban Type: 1 - Original Length, 2 - Custom Length, 3 - Double Length, 4 - Notify Admins Only
// -
// Default: "3"
// Minimum: "1.000000"
// Maximum: "4.000000"
sm_sleuth_actions "1"

// 0 - Inactivated, 1 - Allow all admins with ban flag to pass the check
// -
// Default: "0"
// Minimum: "0.000000"
// Maximum: "1.000000"
sm_sleuth_adminbypass "0"

// How many active bans are allowed before we act
// -
// Default: "0"
sm_sleuth_bansallowed "1"

// 0 - ban all type of lengths, 1 - ban only permanent bans
// -
// Default: "0"
// Minimum: "0.000000"
// Maximum: "1.000000"
sm_sleuth_bantype "1"

// Required: sm_sleuth_actions 1: Bantime to ban player if we got a match (0 = permanent (defined in minutes) )
// -
// Default: "0"
sm_sleuth_duration "0"

// Prexfix for sourcebans tables: Default sb
// -
// Default: "sb"
sm_sleuth_prefix "sb"

[Echo_can]

never mind i figured it out i didnt check the ip for bans dude had 24 bans lol

[IceCucumber]

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).

[FallenNT]

Anybody can fix this plugin and make it compatible with sourcebans 2.0.0-dev?