Tamper → Configuration

Configuration

Call Tamper.Configure once at startup to control how the module handles strikes and kicks. If you never call it, the defaults apply.

Signature

Tamper.Configure(options: \{threshold: number?, autokick: boolean?, onKick: function?})

Options

Option	Default	Description
`threshold`	3	Number of strikes before the autokick or `onKick` callback fires.
`autokick`	`true`	When `true` and no `onKick` is provided, Tamper calls `player:Kick()` automatically at the threshold.
`onKick`	`nil`	Optional callback `(player, strikes, reason)` called instead of the default kick. Use this to log, ban, or apply custom enforcement.

Example

local Tamper = RoExpress.Tamper

Tamper.Configure({
    threshold = 5,
    autokick  = false,
    onKick    = function(player, strikes, reason)
        warn("[Tamper]", player.Name, "reached", strikes, "strikes. Reason:", reason)
        player:Kick("Exploit detected — you have been removed.")
    end,
})

Passive detection

Tamper watches the request pipeline automatically. A malformed packet — missing required fields, wrong types, or an invalid method string — issues an automatic strike and logs the reason. You do not need to configure anything to enable this; it runs as long as Tamper is loaded.

Version mismatches are handled separately and do not go through the strike system. A mismatched version token results in a silent drop with no strike. See Version Checking.

Configuration

Signature

Options

Example

Passive detection

See also