Jump to content
Infinity Gaming

1 Screenshot

About This File

Cheater Alert

Version: 0.0.3.1
Release date: 07.04.2011
eMail: [email protected]
Twitter: MorpheusXAUT
BFcom.org: MorpheusX(AUT)

Please be aware, that this is still a very early release, far away from being perfect. Be careful using the RemovePlayer-function, as the 100% perfect settings for the cheat-detection algorithm have still not been found!

Installation
Check the "Retrieving login data"-part of this post.
You can either download a zip-file (for manual installation), or use PRoCon's Packages-system (for automatic installation).
If you have downloaded the zip-file, simply extract the content of it to your PRoCon-folder.
If you are using the PRoCon Packages-system, click the 'Packages'-Tab on PRoCon's startpage and select CheaterAlert.

Description
Please be aware that the use of this plugin might break the BFBC2 Rules of Conduct.
Please ensure you have read and understood those rules before using the plugin! The plugin's author is not responsible for any actions done or harm taken by this plugin!

Cheater Alert is an attempt to provide another cheat-detection system beside PunkBuster.
This plugin uses some algorithms and simple mathematics to check players and filter out cheaters.
Although the plugin uses several different security-levels, there is still the possibility to falsely detect a player, although this risk should be very small.

If you find any bugs, mistakes or even crashes, please report immediatelly so the error can be fixed soon. You can either contact the author directely (see start of this post) or leave a post within the BFcom.org or phogue.net forums.

Setting up the mySQL-connection
Since Cheater Alert keeps in touch with a mySQL-Server to check you login data and exchange some information, you will have to install the ODBC-connector on the machine the plugin is running on.

Since all data is stream to the same database, you can skip the server-setup part and just concentrate on the connector.
You can find the necessary connection-data within the plugin's description.
Confirm all settings with 'OK' and your ODBC-configuration is done. Please note that this just has to be done once, but on every computer using this plugin.
If you are using a PRoCon Layer Server hosted by any kind of provider, you must nag them to do those steps (setting up the connector on your local machine will NOT solve the problem, unless you keep your computer and PRoCon running all the time.)

Configuring PRoCon's plugin settings
Cheater Alert needs to be able to connect to 2 hosts to do all work properly.
Since connections created by plugins are normally blocked due to security reasons, you will have to alter some settings. Again, this has to be done on the machine running the plugin. If you are using a PRoCon Layer Server hosted by any kind of provider, you must nag them to do those steps (altering the plugin settings on your local machine will NOT solve the problem, unless you keep your computer and PRoCon running all the time.)

Variant 1: disabling sandbox mode

  • This variant is the easier one. You will have to disable PRoCon's sandbox-mode, which will remove the connection-blockades. This is easier to configure, but a little less secure.
  • To do so please do the following:
  • Click 'Tools' (in the upper right corner of your PRoCon-window
  • Click 'Options'
  • Click the 'Plugins' tab within the new window
  • Click the dropdown-list under 'Plugin security' and select 'Run plugins with no restrictions'
  • Close the Options-window by clicking 'Close' and restart your PRoCon


Variant 2: adding the necessary hosts to the exceptions

  • Click 'Tools' (in the upper right corner of your PRoCon-window
  • Click 'Options'
  • Click the 'Plugins' tab within the new window
  • Click inside the 'Trusted host/domain' field and enter 'http://api.bfbcs.com'
  • Click inside the 'Port' field and enter '80'
  • Make sure the right line appears in the list below
  • Click the checkbox 'Allow all outgoing ODBC connections' (has to be checked)
  • Close the Options-window by clicking 'Close' and restart your PRoCon


Setting up Cheater Alert
Once you have done above steps, you are ready to finally configure the plugin itself.
All options will be explained in the pollowing paragraph:

1. Login

  • Login Status: stats the current login status. After entering your login data, please click this dropdown-list and select 'Login'
  • Login Name:the username, which you requested to log in with
  • Login Password: the password, which you requested to log in with


2. General Settings

  • I have read the description: just a check to make sure you have read this 😉
  • Spam Console?: shows messages within the plugin-console
  • Clean up data automatically? (recommended): toggles whether the plugin deletes all stored data every few rounds. This is recommended to prevent lag
  • Cleanup speed: toggles the cleanup-speed
  • Turn Debug Mode on?: shows some extra debug-messages within the plugin-console[/*:m:22hj4mvi]
  • Log Data to file?: logs some values to a .txt-file stored on the machine the plugin is running on
  • Alter plugin variables (use with caution!): tiggkes the ability to change the plugin's cheat-detection variables. Please be careful with this because the plugin hasn't been tested with other values and might not react as wished
  • Remove Player?: toggle the plugin's automatic player-removing system, if a cheater is detected
  • Stream to database? (recommended!): Sends stats about kills, deaths, headshots, ... to the database. This is recommended to help improve the plugin


3. Cheat-detection Variables

  • Ingame max KDR: if this value is exceeded, a player will be treated as suspicious concerning his ingame-KDR
  • Ingame max Kills: if this value is exceeded, a player will be treated as suspicious concerning his ingame-kills
  • Ingame max percentage of headshots: if this value is exceeded, a player will be treated as suspicious concerning his ingame-headshots
  • Ingame max kills per minute: if this value is exceeded, a player will be treated as suspicious concerning his ingame-KPM
  • Global max KDR: if this value is exceeded, a player will be treated as suspicious concerning his global KDR


4. Remove Player

  • Ban Player?: toggles whether a player will be kicked ('No') or banned ('Yes')
  • Ban Player's GUID: toggles whether a player will be banned using his name ('No') or his EA-GUID ('Yes')
  • Ban Player's PB-GUID: toggles whether a player will be banned using his EA-GUID ('No') or his PunkBuster-GUID ('Yes')
  • Permanently Ban Player?: toggles whether a player will be time-banned ('No') or banned permanently ('Yes')
  • Ban time (minutes): time in minutes, whicha player will get banned
  • Kick Reason: message displayed to a player when he is kicked
  • Ban Reason: message displayed to a player when he is banned temporarely. Use %bt% to include the ban-time
  • Perm Ban Reason: message displayed to a player when he is banned permanently


5. White- and Blacklisting

  • Player White List: exact ingame-name (case-sensitive, without clantag) of players, who get excloded from the cheat-detection algorithms
  • Clan White List: exact ingame-clantag (case-sensitive) of players, who get excluded from the cheat-detection algorithms
  • Clan Black List: exact ingame-clantag (case-sensitive) of players, who get kicked immediatelly when wearing this tag


To-Do list

  • fix Suspectedness-algorithm (thing about a better status-system :-D)
  • clean up unneeded stuff (spam console/debug mode, some doubled-checks)
  • optimize data sent to mySQL-table
  • optimize stored player data (guids, names, ids)
  • improve threading system
  • implement email notification feature
  • improve White- and Blacklistung system (custom messages, kick/ban, make case-insensitive)


Known bugs/issues
SOLVED: White- and Blacklisting system doesn't work (plugin doesn't save entered data)[/*:m:22hj4mvi]

Special thanks
There are pretty some people, who have helped me with this plugin in some kind. Please give me a shout if I missed someone.
This list is in no specific order:

  • phogue - for creating PRoCon and helping me out with programming a lot
  • XpKiller - for helping me much with ODBC-programming and SQL-stuff
  • Phil_K - for help with programming
  • Zaeed - for help with programming and some ideas
  • micovery - for help with programming and the great idea with the security-system
  • blactionhero - for help with programming and some ODBC- and SQL-help
  • DaBIGfisH - for a killrate-codesnippet
  • haclevan - for letting me test the plugin on his server and streaming stats
  • da_mike - for streaming stats
  • d1ApR1l - for creating BFBCS and the stats-API
  • all others, who gave me ideas and motivation to code this plugin

User Feedback

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
×
×
  • Create New...