Event

anticheat:component

Server

Fired when a peer changes a model component transform on an entity it does not own

Signal

"anticheat:component"

This signal is only fired on the server.

  • Trigger — fired when the server rejects data from a peer; it never kicks, your script decides.
  • Throttling — one signal per peer and reason per second; count is the violations since the last signal.
  • Repeated reports — a single report can be harmless, act on a repeated count, not the first report.
  • Kicking — use core.engine.disconnect_peer to kick a peer.

Arguments

TypeNameDescription
intpeer_idId of the peer that sent the rejected data
stringreasonWhy it was rejected, see below
intnet_idNet id of the entity involved
intcountViolations of this reason since the last signal, at least 1

Reasons

ReasonDescription
unauthorizedThe peer changed a component transform on an entity it is not the syncer of

Example

Log component violations
util.event.on("anticheat:component", function(peer_id, reason, net_id, count)
    core.engine.print("warn", "Peer " .. peer_id .. " component violation on", net_id, "x" .. count)
end)

On this page