Ban System
sWatch takes extra meassures befor banning a player.
Hooks
Functions
If a ban is in progress, the player is imune to kicks or bans with other reasons.
sWatch.banPlayer
Used to ban a online or offline player.
Player is offline: Offline player will be set to banned on sight. The next time the player enters the server he will be banned.
Player is online: We send different payloads to the client and after some seconds he will get banned.
Arguments
(Player|SteamID) player
(String) reason - Displayed to the banned client (leave empty for default reason)
(String) comment - Add some details to the ban. Will only be visible for admins in the menu.
(String) internalReason - use
"admin_manual"
or create a new detection inconfig/detections.lua
file. If no internal reason is given, an error will occur.(Boolean) force (optional) - ignores if detection is disabled or invalid
Example
sWatch.banPlayer(
"STEAM_0:1:1234567",
"Please just go", // Reason to display client
"I didn't like him", // Internal comment
"admin_manual"
)
sWatch.kickPlayer
Arguments
(Player|SteamID|SteamID64) player
(String) reason - Displayed to the client (leave empty for default reason)
(String) internalReason - Same as
internalReason
in sWatch.banPlayer
sWatch.getFingerprint
A Fingerprint is collected from every client. If a player gets banned, his fingerprint will get stored together with the ban to prevent a bypass. Fingerprint will get requested from client on swatch_networking_playerauthenticated
and is avaliable after a few seconds.
Arguments
(Player|SteamID|SteamID64) player
Returns
(Table) fingerprint
sWatch.getIndicators
Like sWatch.getFingerprintwe collect typical indicators on players. (Newly installed game, use of developer commands, ...)
Arguments
(Player|SteamID|SteamID64) player
Retruns
(Table) indicators
Last updated