API
Security
Available exclusively on the Studio plan. Use
FluxServer.Security and FluxClient.Security to log exploit attempts and anomalous behavior for automatic clustering.Signatures
FluxServer.Security(player: Player, severity: AnomalySeverity, message: string, payload: LogPayload?)
FluxClient.Security(player: Player, severity: AnomalySeverity, message: string, payload: LogPayload?)Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| player | Player | Yes | The Roblox Player instance associated with this anomaly. |
| severity | AnomalySeverity | Yes | The severity level of the anomaly (e.g., FluxServer.severity.high or FluxServer.severity.critical). Available values are low, medium, high, and critical. |
| message | string | Yes | A short description of the suspicious activity. |
| payload | LogPayload | No | JSON-serializable extra fields, such as player speed or coordinates. |
Automatic Clustering
Logs sent via the Securitymethod go through standard logging like any other log — they appear in your normal log stream — but are flagged as anomalies and given the highest send priority, so they are the last to be dropped if the queue fills under load. Flux automatically groups them by the player's UserId and severity and surfaces them in the Security tab of your dashboard, creating a real-time moderation queue.
Examples
-- Flagging a potential speed exploit
FluxServer.Security(player, FluxServer.severity.high, "Speedhack detected", {
speed = 250,
maxAllowed = 16
})
-- LocalScript: flagging client anomalies
FluxClient.Security(player, FluxClient.severity.low, "Suspicious memory spike", { usage = 2048 })