Event

anticheat:dimension

Server

Fired when a peer sends a dimension change it is not allowed to send

Signal

"anticheat:dimension"

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 the dimension of an entity it is not the syncer of
invalidThe dimension is outside the valid range
attachedThe entity is attached to a parent, so it follows its dimension

Example

Kick on out-of-range dimensions
util.event.on("anticheat:dimension", function(peer_id, reason, net_id, count)
    if reason == "invalid" then
        core.engine.disconnect_peer(peer_id)
    end
end)

On this page