Page 1 of 48 12311 ... LastLast
Results 1 to 10 of 509

Hybrid View

  1. #1
    Plugin Developer
    Join Date
    May 2012
    Location
    germany, flensburg
    Posts
    301

    CheatDetector 0.5.2.1

    CD - CheatDetector [BF3/BF4]

    Description
    Stats Check
    This plugin tries to detect cheaters by their BF3 Battlelog Stats. This is done in the following way:
    When a new player has joined (by detecting new entries in the playerlist. not by the playerjoined event, to prevent spamming) his stats are fetched from his Battlelog page (3 requests).
    This is done for 1 player every 30 seconds, to not trigger any restrictions on the Battlelog side using a fifo-queue (first in, first out. or fcfs (first come, first served))
    Then every weapons stat (with more than 130 kills, or more headshots than kills with more than 20 kills) is checked against a collection of averages to decide if its normal, suspicious or impossible.

    The following stats are checked:
    Player SPM (score per minute)
    Weapon k/m (KPM, kills per minute)
    Weapon hs/k (HSPK, headshots per kill)
    Weapon k/h (KPH, kills per hit)
    Weapon accuracy

    Strict Mode: A player is considered cheating if he has 4 suspicious stats or 1 IMPOSSIBLE stat.
    Normal Mode: A player is considered cheating if he has 5 suspicious stats or 1 IMPOSSIBLE stat and 1 suspicious stat.

    Example:
    Code:
    1:  [10:10:13 19] CD - IMPOSSIBLE STATS: Mong0lFPS M60 k/h: 100% (5,01)
        [10:10:13 19] CD - IMPOSSIBLE STATS: Mong0lFPS M60 k/m: 18,22 (16,71)
        [10:10:13 19] CD - IMPOSSIBLE STATS: Mong0lFPS M240 k/h: 100% (4,98)
        [10:10:13 21] CD - IMPOSSIBLE STATS: Mong0lFPS M240 k/m: 15,81 (14,64)
    5:  [10:10:13 26] CD - IMPOSSIBLE STATS: Mong0lFPS spm: 9475,55
        [10:10:13 26] CD - SUSPECTED CHEATING: Mong0lFPS 99%
        [10:10:13 26] ------------------------
        [10:10:43 46] CD - suspicious stats: Kershalt007 Pecheneg hs/k: 67,69% (2,77)
        [10:10:43 46] CD - IMPOSSIBLE STATS: Kershalt007 Pecheneg k/m: 10,44 (8,7)
    10: [10:10:43 47] CD - suspicious stats: Kershalt007 M60 hs/k: 74,26% (3,06)
        [10:10:43 47] CD - IMPOSSIBLE STATS: Kershalt007 M60 k/m: 10,76 (9,88)
        [10:10:43 47] CD - suspicious stats: Kershalt007 M27 hs/k: 72,02% (2,97)
        [10:10:43 47] CD - suspicious stats: Kershalt007 XP2 LSAT hs/k: 69,3% (3,15)
        [10:10:43 50] CD - SUSPECTED CHEATING: Kershalt007 99%
    15: [10:10:43 50] ------------------------
        [10:11:14 59] CD - IMPOSSIBLE STATS: UMadPanda PDR hs/k: 137,36% (6,53)
        [10:11:14 60] CD - IMPOSSIBLE STATS: UMadPanda Taurus 44 hs/k: 163,16% (6,7)
        [10:11:14 60] CD - IMPOSSIBLE STATS: UMadPanda F2000 hs/k: 125,06% (5,28)
        [10:11:14 60] CD - IMPOSSIBLE STATS: UMadPanda P90 hs/k: 87,93% (4,4)
    20: [10:11:14 65] CD - SUSPECTED CHEATING: UMadPanda 99%
        [10:11:14 65] ------------------------
    As you can see in the first line, the weapon "M60" on the player "Mong0lFPS" has a "k/h" (kills per hit ratio) of 100% (422 hits, 422 kills), which is 5,01 times higher than the average k/h on the M60. This is considered impossible.
    Line 6 shows the summary of all checks for the player "Mong0lFPS". 99% cheating so this player would be kicked/banned or an admin notified.
    Weapons with more headshots than kills (except shotguns, rockets and the like) and more than 20 kills will be treated as IMPOSSIBLE (=cheating).

    Example:
    weapon asval: player x has 300 kills
    the average hs/k on the asval is 25,85% thats 77 headshots

    suspicious would be having a hs/k of 69,79% which is 209 headshots. (270% above the average)
    impossible would be having a hs/k of 82,72% which is 248 headshots. (320% above the average)

    the table shows what is considered suspicious and impossible
    check suspicious (% above average) impossible (% above average)
    accuracy 320% 370%
    hs/k 270% 320%
    k/h 270% 320%
    k/m 500% 800%
    spm ~340% ~500%
    Live Check
    From version 0.4 CheatDetector features a Live Protection.
    Every 5 minutes all players (except players in the whitelist) will be checked for their headshots per kills (hs/k) and kills per minute (kpm) during their time on your server.
    A player is considered cheating if he has > 91% hs/k or > 8 kpm with at least 20 kills. This is basically (average over all weapons) the same limit CheatDetector uses for Stats Check.
    Note that Live Check does not distinguish between weapons or vehicles. (This is not reported by the game server)

    Example:

    Code:
    [16:15:02] CD - LiveCheck SUSPECTED CHEATING OMonkeyOoOoOo kills: 30 hs: 30 time: 9,59 hs/k: 100% kpm: 3,12
    If 0. Enable Live Check is set to "Yes" these 2 players will be kicked (or banned, depending on your settings).
    For the message displayed to the kicked player %suspiciousstat% will be replaced with "too many hs/k or k/min (CD - LiveCheck)" instead of a certain weapon.
    This will protect your server from cheaters with clean (or resetted) stats. You can see the checks for non-cheaters on debug level >=3.

    Stream players to 247FairPlay.com
    http://www.247FairPlay.com is a website providing stats, forum and ban appeal for my server and my bans.
    Since version 0.4 you can stream the players on your server to a database at 247FairPlay.com. This DB will be used to check the players in addition to the CheatDetector plugin on your server. The plugin will not be blocked by this and errors (for example: you cant reach 247fairplay.com) wont show up in the log. its "fire and forget".
    You can see the requests on debug level >=3.
    These checks include extended stats check, linked accounts, history check to name just a few (note that some of these features are still in development)
    Detected cheater will be banned through the metabans.com account @CheatDetector (http://metabans.com/CheatDetector)

    How do you make use of these checks? Simple: install metabans plugin and follow @CheatDetector to enforce the bans on the detected cheaters. Depending on the usage (and several more restrictions), it might take some time to get checks done.

    You will find further information about the new CheatDetector features in the CheatDetector thread at Procon forums, at 247FairPlay.com forum or here as it develops :-)

    THANK YOU
    THX & Credits go to the following people (and more i'm sure):
    all Procon Devs for Procon and their API :-)
    i-stats.net & symthic.com & bf3stats & cheatometer for their massive DBs of weapon and player values and known cheaters
    Panther for showing how to use that API and other Plugin stuff
    Phil & Phogue & MorpheusX for all their support and tips and letting me nag em :-)
    EBastard & HexaCanon & PapaCharlie & ty_ger & dyn & IAF SDS & all the other for testing, reporting & various tips

    Support & Feedback
    http://www.phogue.net/forumvb/showth...ector-%28CD%29

    Plugin (recommended) Settings
    0. Ban Method and Whitelist and BattlelogCache
    Servertype: BF3/BF4/Automatic. (Automatic)
    TempBan/Ban by name: Not recommended. A Player can easily change their name and join again. (No)
    TempBan/Ban by EA GUID: Recommended. This ID is linked to the player's EA account. Works best with Metabans (Yes)
    TempBan/Ban by PB GUID: Recommended. This ID is linked to the player's cd key (No)
    Whitelist: List of players (ingame-names without clantag) not to check
    Sync ReservedSlots/ServerVIPs: Automatically syncronize the players in the ReservedSlot list with the Plugin Whitelist (Yes)
    Use BattlelogCache if available: Use the Battlelog Cache to reduce traffic (Yes)
    Stream Players to 247FairPlay.com: If enabled CheatDetector will contact http://www.247fairplay.com/cheatdetector.php every 30 minutes to add the players on your server to a database to do stats checks and various other checks. If a cheater is detected, he will be banned through the MetaBans Account @CheatDetector (http://metabans.com/CheatDetector). (Yes)
    Enable Stats Check: Enable the stats check through battlelog. (Yes)
    Enable Strict Mode: When enabled: 1 IMPOSSIBLE or 4 suspicious stats is considered cheating (=kick/ban). When set to NO: 1 IMPOSSIBLE and 1 suspicous or 5 suspicious stats is considered cheating. (NO)
    Enable Live Check: Enable the ckecking of the players hs/k and kpm on your server. (Yes)

    2. Kick
    Enable Kick: No
    Message to be displayed to the kicked player: %playername% will be replaced with the players name. %pbguid% will be replaced with the players PunkBuster GUID. %eaguid% will be replaced with the players EA GUID. %suspiciousstat% will be replaced with the most significant detected stat. (SUSPECTED CHEATING: %playername% %suspiciousstat%)

    3. TBan
    Enable Temp: If temp ban is enabled, no kick will happen (Yes)
    Message to be displayed to the temp banned player: %playername% will be replaced with the players name. %pbguid% will be replaced with the players PunkBuster GUID. %eaguid% will be replaced with the players EA GUID. %suspiciousstat% will be replaced with the most significant detected stat. (SUSPECTED CHEATING: %playername% %suspiciousstat%)
    Length of Temp Ban (min): Length of temp ban in minutes (15)

    4. Ban
    Enable ban: If permanent ban is enabled, no temp ban or kick will happen (No)
    Message to be displayed to the banned player: %playername% will be replaced with the players name. %pbguid% will be replaced with the players PunkBuster GUID. %eaguid% will be replaced with the players EA GUID. %suspiciousstat% will be replaced with the most significant detected stat. (SUSPECTED CHEATING: %playername% %suspiciousstat%)

    5. Notify
    Enable ingame notification: Yell a message to an admin (or any other player) when a player is detected by this plugin (Yes)
    Enable private/public notification: Enable the desired type(s) of notification
    Ingame username: player to receive the ingame notification
    Message to be displayed: Message to be displayed to the ingame playername (CheatDetector - SUSPECTED CHEATING: %playername% %suspiciousstat%)
    Time to display (sec): Time to display the ingame notification in seconds (30)

    6. Debug
    Debug Level (0-5): Debug level adjusting how many debug messages you will see in the plugin console log (1)
    0 - no messages at all (quiet)
    1 - only detections/kicks/bans will be displayed
    2 - will also show log entries for normal players and some queue timeout operation when neccessary
    3 - will also show the queue size and number of players enqueued, adding and removing of players to the playerlist and queue, skipping of whitelisted players, queue timeout operations
    4 - will also show checked and skipped weapons, a lot more internal operations, "expected" errors (dont worry ;-))
    5 - just for development and testing

    Automatic Update Check: Check for Plugin Updates every 3 hours. (Yes)
    Log to file: Log plugin output to a file (CDLogFile.txt) in the Plugin/BF3 directory. Not recommended, this file may get very big and slow your procon down. Only use it to log errors and only use it local (No)
    Filename/Path: Filename and path of the logfile relative to the Procon executable (Plugins/BF3/PBSSELogFile.txt)
    Advanced: DO NOT PLAY WITH THESE VALUES UNLESS INSTRUCTED BY ME OR YOU WILL BREAK THE PLUGIN (NO)

    DO NOT EDIT ANY OF THE BELOW SETTINGS - LAST WARNING - VERBOTEN
    Lazy Queue: When enabled, the plugin will also check players that left the server while being enqueued (No)
    Orange Flag Score per Min: Set the SPM needed to raise a suspicious flag (1200)
    Red Flag Score per Min: Set the SPM needed to raise a IMPOSSIBLE flag (2000)
    Min Kills: Minimum Kills needed for a weapon to be analyzed (200)
    Min Kills (live): Minimum Kills needed for a player to be checked during Live Check (30)
    Max hsklive: Headshots per Kill Percentage needed to raise a IMPOSSIBLE flag during Live Check (0.91)
    Max kmlive: Kills per Minute needed to raise a IMPOSSIBLE flag during Live Check (8)
    Name: List of Players to check when TEST (Option below) is set to Yes
    Test: Check Players listed in NAME (Option Above) (No)
    Retries: Retry stats fetching X times when failed (1)
    Timeout Test: Let all requests to fetch stats fail. Just for testing (No)
    Stream to Master: Settings for streaming to my mysql server. (No)

    Version History (Changelog):
    0.5.2.1
    -Fix: Added placeholders for new Final Stand DLC weapons.
    -Fix: Other minor fixes.

    0.5.2.0
    -NEW: Adjusted cheat detection algorithm to better fit the new averages.
    -Fix: Updated weapon averages (for Dragon's Teeth DLC weapons too).
    -Fix: Added Placeholder for new Knife (KNIFEWEAVER).
    -Fix: When new weapons get added to Battlelog, plugin will no longer spam endless msgs on debug level 1.

    0.5.1.2
    -Fix: Added placeholders for Dragon's Teeth DLC weapons
    -Fix: Increased HS/K used in Live Check to 94%
    -Fix: Fixed some issues with weapon names in ban msgs

    0.5.1.1
    -Fix: Added missing weapons for Naval Strike DLC

    0.5.1.0
    -NEW: Updated used averages (i-stats.net)
    -Fix: Bug in streaming caused some servers to not transmit its additional info (servername, ip, port, servertype) properly
    -Fix: Added missing weapons for Second Assault DLC

    0.5.0.1
    -Fix: Persona ID could not be found for some players.
    -Fix: Changed Include/Exclude VIPs to Sync VIPs
    -Fix: Updated description

    0.5.0.0
    -NEW: BF4 Compatibility
    -NEW: Automatic update check
    -Fix: Increased SPM limits to improve the overall detection
    -Fix: Extended Infos streamed to 247FairPlay.com for later use with stuff :-)

    0.4.3
    -FIX: More headshots than kills will be treated as headshots equal to kills to reduce the chance of false detections.
    -FIX: Increased minimum kills to 200 to reduce the chance of false detections.
    -FIX: Live Check: Increased minimum kills to 30 to reduce the chance of false detections.

    0.4.2
    -NEW: Settings: Enable Strict Mode (When enabled: 1 IMPOSSIBLE or 4 suspicious stats is considered cheating (=kick/ban). When set to NO: 1 IMPOSSIBLE and 1 suspicous or 5 suspicious stats is considered cheating.)
    -FIX: More headshots than kills are only considered IMPOSSIBLE (or suspicious) if they exceed the average by 320% (270%). See https://forum.myrcon.com/showthread....ll=1#post75230.

    0.4.1
    -FIX: Increased minimum kills needed for weapons with more headshots than kills back to 130.

    0.4
    -NEW: Live Check: CheatDetector will now monitor the players on your server for headshots per kills and kills per minute. Cheating is considered >91% HS/K or >8 KPM with more than 20 kills. A check is made every 5 minutes. Whitelist and messages apply here too. (0. Ban Method and Whitelist and BattlelogCache -> Enable Live Check)
    -NEW: Stream Players to 247FairPlay.com: If enabled CheatDetector will contact http://www.247fairplay.com/cheatdetector.php every 30 minutes to add the players on your server to a database (the plugin will not be blocked by this and errors (for example: you cant reach 247fairplay.com) wont show up in the log. its "fire and forget"). This DB will be used to do stats checks and various other checks. If a cheater is detected, he will be banned through the MetaBans Account @CheatDetector (http://metabans.com/CheatDetector).
    -FIX: Stats Check: Weapons with more headshots than kills (except shotguns, rockets and the like) and more than 20 kills will be treated as IMPOSSIBLE (=cheating).
    -NEW: Settings: Enable Live Check.
    -NEW: Settings: Enable Stats Check.
    -NEW: Settings: Stream Players to 247FairPlay.com
    -NEW: Settings: Exclude Non-ReservedSlots/ServerVIPs: will automatically remove players from the plugins whitelist that are not in your ReservedSlots List
    -FIX: Several internal code improvements.

    0.3
    -NEW: You can now use Battlelog Cache to reduce traffic. (0. Ban Method and Whitelist and BattlelogCache -> Use BattlelogCache if available)
    -FIX: The Output on certain debug levels have been adjusted to be not so spamming.
    -FIX: 2 Typos in Weapon Names have been fixed (M1911 Tactical) which caused this weapon to not be analyzed for k/h and k/m.
    -FIX: Under certain circumtances endless ingame notification could happen. This is now fixed.
    -FIX: When a player is banned (TBan and Ban) a Kick will make sure the player is gone.
    -FIX: Added placeholders %pbguid% and %eaguid% to the messages.
    -FIX: Increased the max TBan time to 100 years (was 1 year), but you might as well use permanent there :-)
    -FIX: Several internal code improvements.

    0.2.1
    -NEW: You can now setup the ingame notification (4. Notify) in detail.
    -FIX: Tiny update to the scores to find the best reason (most suspicious/impossible stat) to be used in various messages.
    -FIX: SPM is now only taken into account if the playtime is above 1 hour.
    -FIX: small code updates.

    0.2
    -UPDATE: You can now download/update CheatDetector directly through your procon gui.

    0.1.2
    -FIX: The plugin will now automatically detect when the BF3 Battlelog Request Limit is reached. Then it will increase the queue timeout. The timeout will then be decreased step by step to normal.
    -FIX: An error happened when there were multiple detections with the same score. This is now fixed
    -FIX: not that important error messages are now displayed properly (Debug level 2, 3, 4)

    0.1.1
    -FIX: Plugin now identifies itself properly to Battlelog

    -NEW: Option to add multiple usernames to get notified (4. Notify -> ingame username)
    0.1
    -Public release

    Known Issues
    Cheat Detection
    Since this plugin tries to detect cheaters using their BF3 Battlelog stats, it is limited to that data. If a cheater got his stats reset, there is no way for this plugin (as of now version 0.1.2) to detect the cheater.
    On the other hand, this plugin might detect someone as a cheater who is not cheating.
    Workaround (cheater not detected): None. Inform me about this issue. Maybe i will add other data sources for cheat detection in the future.
    Workaround (normal player detected as cheater): Add this player to your whitelist and inform me about this false positive.

    Whitelist
    If you add a player to your ReservedSlots/ServerVIP List they might not show up in the whitelist setting immediately. However you can be sure they are added and processed. I think this is because Procon GUI does not reload the setting when its not changed in the GUI. Just reopen the Plugins Tab and they should be displayed. Or restart Procon on your PC (NOT the layer server, just the exe on your PC) and they will show up.
    Workaround: Not really needed, however if someone knows a solution i would like to know it too :-)

    Logfile
    This file may get very big and slow your procon down. Only use it to log errors and only use it local. The directory must also exist and be writeable by your procon.

    Planned Features
    -Detect cheaters that had their stats reset

    there are certain limitations for these features:
    http://www.phogue.net/forumvb/showth...ll=1#post63715
    Attached Files Attached Files
    Last edited by grizzlybeer; 19-05-2016 at 09:43.

  2. #2
    Plugin Developer
    Join Date
    May 2012
    Location
    germany, flensburg
    Posts
    301
    You can find further Infos about CheatDetector here:
    http://www.247FairPlay.com

    You can find bans produced by this plugin (on my server) here:
    http://metabans.com/CheatDetector

    or feel it from the player side here :-)
    http://battlelog.battlefield.com/bf3...Bans-MetaBans/
    Last edited by grizzlybeer; 02-05-2013 at 18:44. Reason: added website

  3. #3
    Nice, I will definitely give this a run. BTW Metabans seems down again?

  4. #4
    Plugin Developer
    Join Date
    May 2012
    Location
    germany, flensburg
    Posts
    301
    Quote Originally Posted by Kinsman View Post
    Nice, I will definitely give this a run. BTW Metabans seems down again?
    try it and tell me what you think :-)
    yes. metabans is down at the moment.

  5. #5
    Quote Originally Posted by grizzlybeer View Post
    try it and tell me what you think :-)
    yes. metabans is down at the moment.

    we did run a full backup of the database. Metabans is up.


  6. #6
    Looks nice! Will try it out and report back if I experience any issues (or success maybe)

    Got a question.. is it possible to add multiple Ingame usernames under the 4. Notify section?
    Last edited by Flaxe; 15-12-2012 at 14:14.

  7. #7
    Plugin Developer
    Join Date
    May 2012
    Location
    germany, flensburg
    Posts
    301
    Quote Originally Posted by Flaxe View Post
    Got a question.. is it possible to add multiple Ingame usernames under the 4. Notify section?
    in this version (0.1) you can only enter 1 username. sorry.
    i will add the option to enter more names in the next update.

    Quote Originally Posted by MorpheusX(AUT) View Post
    You will most likely have to change your stats fetching mechanisms in the nearer future due to request limits and problems coming with that.
    thx for the info. i already noticed the restrictions, but at the moment it seems to work with 1 player every 30 seconds. if there is a need for change in the future, i will change it :-)

  8. #8
    Quote Originally Posted by grizzlybeer View Post
    in this version (0.1) you can only enter 1 username. sorry.
    i will add the option to enter more names in the next update.
    Ok! Make it one username per row. Then it will be easy to just copy other username lists from other plugins

  9. #9
    "I was a genuinely nice person before I joined this community"
    Join Date
    May 2010
    Location
    Austria
    Posts
    3,273
    Great, another plugin hammering the already "overloaded" Battlelog with requests.
    You will most likely have to change your stats fetching mechanisms in the nearer future due to request limits and problems coming with that.


    Before posting: Have you read the MANUAL?
    Before posting: Have you used the SEARCH?

    I will not provide support through PMs or TeamSpeak. Please post your questions in our forums.


  10. #10
    Quote Originally Posted by MorpheusX(AUT) View Post
    Great, another plugin hammering the already "overloaded" Battlelog with requests.
    You will most likely have to change your stats fetching mechanisms in the nearer future due to request limits and problems coming with that.
    I wonder if it's possible to have a separate plug-in just for fetching stats from various sources like battlelog and bf3stats and have other plug-ins request data from this plug-in? This way we reduce the load on the data sources and make procon lighter and faster.

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •