[StevoTVR]

VAC Status Checker

This plugin checks for VAC, game, Steam Community, and trade bans on the accounts of connecting clients and takes the desired action. Useful for admins who want to block access to people for bad behavior outside the server.

Get plugin | View source | View changelog



Requirements

• One of the below extensions:
  • SteamWorks
  • SteamTools
  • Socket
• A Steam Web API key obtained from https://steamcommunity.com/dev/apikey
• SourceMod 1.7+

Installation

1. Download vacbans-x.x.x.zip
2. Extract to addons/sourcemod
3. Set sm_vacbans_apikey to your Steam Web API key

Console Variables

// Actions to take on detected clients
// Add up the options from the list:
// 1:  Log to sourcemod/logs/vacbans.log
// 2:  Kick
// 4:  Ban
// 8:  Display message to admins
// 16: Display message to all players
// -
// Default: "3"
// Minimum: "0.000000"
// Maximum: "31.000000"
sm_vacbans_actions "3"

// The Steam Web API key used by VAC Status Checker
// https://steamcommunity.com/dev/apikey
// -
// Default: ""
sm_vacbans_apikey ""

// How long in days before re-checking the same client
// -
// Default: "1"
// Minimum: "0.000000"
sm_vacbans_cachetime "1"

// The named database config to use for caching
// -
// Default: "storage-local"
sm_vacbans_db "storage-local"

// Enable Steam Community ban detection
// -
// Default: "0"
// Minimum: "0.000000"
// Maximum: "1.000000"
sm_vacbans_detect_community_bans "0"

// Enable economy (trade) ban detection (0 = disabled, 1 = bans only, 2 = bans and probation)
// -
// Default: "0"
// Minimum: "0.000000"
// Maximum: "2.000000"
sm_vacbans_detect_econ_bans "0"

// Enable game ban detection
// -
// Default: "0"
// Minimum: "0.000000"
// Maximum: "1.000000"
sm_vacbans_detect_game_bans "0"

// Enable VAC ban detection
// -
// Default: "1"
// Minimum: "0.000000"
// Maximum: "1.000000"
sm_vacbans_detect_vac_bans "1"

// Ignore VAC bans older than this many days (0 = disabled)
// -
// Default: "0"
// Minimum: "0.000000"
sm_vacbans_vac_expire "0"

// Ignore VAC bans issued before this date (format: YYYY-MM-DD)
// -
// Default: ""
sm_vacbans_vac_ignore_before ""

Console Commands

• sm_vacbans_reset - Clears the cache database. Run from server console or client with sm_rcon access.
• sm_vacbans_whitelist <add|remove|clear> [SteamID] - Run from the server console or client with sm_rcon access to control the whitelist:
  • add <SteamID> - adds a SteamID for the plugin to ignore
  • remove <SteamID> - removes a SteamID from the whitelist
  • clear - removes all SteamIDs from the whitelist
• sm_vacbans_list - Lists the bans of connected clients. Admins with access to this also see the connect messages when sm_vacbans_action is 2.

Override Commands

• sm_vacbans_immunity - Users with access to this command will not be checked for bans (defaults to RCON access)

Notes

• All account data comes from the Steam Web API.
• This works with SourceBans.
• Data is logged to sourcemod/logs/vacbans.log.

Credits

• voogru - finding the algorithm for converting SteamIDs
• berni & StrontiumDog - the function that converts SteamIDs
• Cripix - French translation
• Dreizehnt - Russian translation

[Sillium]

Here's a german Version:

"Phrases"
{
    "Kicked"
    {
        "de"        "Du wurdest aufgrund einer früheren VAC Verletzung gekickt."
    }
    "Banned"
    {
        "de"        "Du wurdest aufgrund einer früheren VAC Verletzung gebannt."
    }
    "Banned_Server"
    {
        "#format"    "{1:s}"
        "de"        "{1} aufgrund einer früheren VAC Verletzung gebannt."
    }
}

[FlyingMongoose]

The problem with this is, there are some odd half-vac bans out there, some old false positives thanks to early versions of x-fire, and a number of other oddities. I have a friend who didn't hack, but he used x-fire, now he's vac banned on all non-source servers that are VAC enabled (IE HL1 based servers). But he can play on source. Ultimately though, it's a nice plugin.

[devicenull]

Originally Posted by FlyingMongoose The problem with this is, there are some odd half-vac bans out there, some old false positives thanks to early versions of x-fire, and a number of other oddities. I have a friend who didn't hack, but he used x-fire, now he's vac banned on all non-source servers that are VAC enabled (IE HL1 based servers). But he can play on source. Ultimately though, it's a nice plugin.

Valve reversed these bans, just like they did for HLSS and Wine.

[FlyingMongoose]

I wish that were the case for my friend, they never reversed him. And he did contact support. Their immediate response: "VAC IS NEVER WRONG" (in all caps just like that)

[tcviper]

Thought I love what you wrote this plugin can be dangerous as it wasnt supposed to be doing this across engines. If people do something wrong in one engine it affects all games under that engine and not the others. I personally think putting this on servers would be a bad idea.

[jack_wade]

Here comes the spanish translation ;)

"Phrases"
{
    "Kicked"
    {
        "es"        "Has sido kickeado debido a una violación de VAC anterior."
    }
    "Banned"
    {
        "es"        "Has sido baneado debido a una violación de VAC anterior."
    }
    "Banned_Server"
    {
        "#format"    "{1:s}"
        "es"        "{1} baneado debido a una violación de VAC anterior."
    }
}

[StevoTVR]

Originally Posted by tcviper Thought I love what you wrote this plugin can be dangerous as it wasnt supposed to be doing this across engines. If people do something wrong in one engine it affects all games under that engine and not the others. I personally think putting this on servers would be a bad idea.

I don't see why. Some server admins would prefer not to separate hackers based on engine. To them, a hacker is a hacker.

[tcviper]

thats why we have steambans.com

[dirtyjob]

so if set to "2" it only logs players that have a prior cheat infraction?