Configuration

SafeGuard is configured in two places:

Dashboard → Rules: with the cloud connected, this is where each server's detections and punishments are set. Every change is versioned and audited, reaches the server within seconds, and you can Restore an older version from History.
`config.lua`: framework, staff, language, local evidence and alerts, and the protection policy used without the cloud (Config.Protection). sg reload applies changes without a restart.

Secrets (license key, Discord webhook) never go in config.lua: they go in server.cfg with set.

Detections

In Rules → Detections you can switch any detection off or change its sensitivity (0 = most tolerant, 100 = most aggressive). If a detection gives false positives on your server, lower its sensitivity rather than switching it off, and mark the wrong detections as false positive: SafeGuard learns and gives them less weight.

Punishments

Punishments depend on the player's risk (0–100), which adds up the weight of each detection and decays over time. The default rules:

Rule	When	What happens
honeypot	Honeypot event triggered	Quarantine, staff review, screenshot
extreme	Risk ≥ 95 and "ban gate" open	Permanent ban
critical	Risk ≥ 80	Quarantine, staff review, screenshot
high	Risk ≥ 60	Staff review
suspicious	Risk ≥ 40	Watch

The ban gate protects against unfair bans: it only opens with at least one server-verified signal at 80% confidence or more, or with signals in two independent categories. Signals that only come from the client never lead to an automatic ban. Quarantine means the player stays connected but cannot deal damage, spawn entities or earn money until released.

For the first weeks we recommend punishments with staff review only, to see how detections behave on your server before enabling automatic bans.

Recommended lists and traps

On by default; you can switch them off in Rules:

Recommended weapons: railgun, ray guns, minigun and launchers are removed from whoever has them.
Recommended props: huge props menus drop on players (ferris wheel, windmill, UFO, cage).
Recommended explosions: blimp, orbital cannon, explosive ammo and others roleplay servers do not have.
Exploit traps: catch menus firing the payout, item and jail events of popular scripts your server does not run. Events of scripts you run are never trapped.

If your server really uses one of those weapons, props or explosions, switch the list off or add the model to Allowed models.

Bypasses

In Rules → Bypasses you can exempt a player from some categories for a while (for example an event with teleports). Staff with safeguard.bypass (or the configured framework permission) are never scored.

config.lua (local mode)

Config.Protection = {
    movement = { maxFootSpeed = 14, teleportDistance = 120, vehicleHijack = true },
    weapons = { recommendedBlacklist = true, blacklist = { 'weapon_rpg' }, inventoryCheck = true, inventoryIgnored = { 'weapon_flashlight' } },
    entities = { recommendedModels = true, blockedModels = { 'prop_beach_fire' }, attachAllowedModels = { 'p_cs_cuffs_02_s' } },
    explosions = { recommendedTypes = true, maxPerWindow = 5 },
    eventShield = { exploitProbes = true, honeypots = { 'myserver:adminGiveMoney' }, fanout = { maxDistinct = 20, windowMs = 5000 } },
    combat = { maxKillsPerMinute = 8 },
    detections = { ['movement.spectate'] = { enabled = false } },
}

The names are the same as in the dashboard. Unknown names are reported in the console, so typos never go unnoticed.

PreviousDashboard NextFrameworks