UNDER THE HOOD

Everything itwatches for.

The full catalogue, the scoring model behind every ban, and the APIs you can build on. Nothing here is marketing — it is read straight from the shipped product.

Detection catalogue

Nothing vague. 88 named checks, and counting.

This is the real catalogue the resource ships with — the same names, descriptions, severities and default actions you will see in the configuration panel. Every one of them can be switched off, re-thresholded or re-pointed at a different action, per server.

Detections

14 categories

Ban by default

the rest kick, flag or log

Hold per-player state

the others are stateless

Flagged, never auto-banned

high false-positive risk

Detection	Category	Runs on	Severity	Default
Aimbot — Camera Snap`aimbot.snap` Camera heading and pitch jump onto a player hitbox faster than a human wrist can move, repeatedly.	Aimbot	Client	High	ban
Silent Aim`aimbot.silent` A shot registers on a target the shooter was never aiming at — the bullet vector and the camera vector disagree.	Aimbot	Client + server	Critical	ban
Aimbot — Sustained Tracking`aimbot.tracking` The crosshair holds sub-degree lock on a moving target across many frames with no human correction jitter.	Aimbot	Client	High	ban
Damage Through Geometry`aimbot.no_line_of_sight` Damage is dealt between two points with solid world geometry in between and no penetrable material.	Aimbot	Server	Critical	ban
Triggerbot`aimbot.triggerbot` Trigger pulls land inside an impossibly tight window of the crosshair crossing a hitbox.	Aimbot	Client	High	ban
Rapid Fire`combat.rapid_fire` Shots leave the weapon faster than its defined rate of fire allows.	Combat	Server	High	ban
Damage Modifier`combat.damage_modifier` A single hit removes more health than the weapon can deal at that range and body part.	Combat	Server	Critical	ban
No Recoil`combat.no_recoil` The recoil recovery pattern is mathematically flat across a sustained burst.	Combat	Client	Medium	kick
No Spread`combat.no_spread` Bullet spread has been zeroed through weapon asset modification.	Combat	Client	High	ban
Infinite Ammo`combat.infinite_ammo` Ammunition does not decrease across sustained fire, or exceeds the weapon maximum.	Combat	Server	High	ban
Melee Reach`combat.melee_range` Melee damage lands well beyond the reach envelope of the equipped weapon.	Combat	Server	High	ban
Explosion Spam`combat.explosion_spam` An unreasonable number of explosions are owned by one player in a short window.	Combat	Server	Critical	ban
Blacklisted Explosion Type`combat.blacklisted_explosion` A player owns an explosion of a type no legitimate script on the server produces.	Combat	Server	Critical	ban
Impossible Headshot Ratio`combat.headshot_ratio` Sustained headshot ratio across a large sample sits far outside the server-wide distribution.	Combat	Server	Medium	flag
Weapon Damage Native Abuse`combat.weapon_damage_native` SetWeaponDamageModifier or an equivalent native was called from an unregistered source.	Combat	Client	Critical	ban
Speed Hack`movement.speed_hack` Ground speed on foot exceeds the maximum achievable value for the current ped and animation state.	Movement	Server	High	ban
Teleport`movement.teleport` Position changes by a distance that could not be travelled in the elapsed time by any means.	Movement	Server	High	ban
Noclip`movement.noclip` The ped moves through collision, or floats unfrozen with collision disabled.	Movement	Client + server	Critical	ban
Fly Hack`movement.fly` Sustained altitude with no supporting entity, parachute or fall state.	Movement	Client + server	Critical	ban
Super Jump`movement.super_jump` Jump apex exceeds the engine maximum for the current ped.	Movement	Client	High	ban
Freecam`movement.freecam` A scripted camera is detached from the ped and moving under player input outside a known cutscene.	Movement	Client	High	ban
Vehicle Speed Modified`movement.vehicle_speed` A vehicle exceeds its handling top speed by more than the configured tolerance.	Movement	Server	High	ban
Gravity Modified`movement.gravity` World or entity gravity was changed by an unregistered source.	Movement	Client	High	ban
Ragdoll Immunity`movement.ragdoll_immunity` The ped refuses to ragdoll under forces that always ragdoll a legitimate ped.	Movement	Client	Medium	kick

Showing 24 of 88

Critical30

−100 Integrity on a confirmed hit

High35

−40 Integrity on a confirmed hit

Medium17

−18 Integrity on a confirmed hit

Low5

−8 Integrity on a confirmed hit

Info1

−3 Integrity on a confirmed hit

Integrity Score

Ban the pattern, not the moment.

Every player carries a 0–100 behavioural score. One ambiguous hit costs a few points; a cheat that keeps tripping the same check converges on a ban on its own. It is what lets ARGUS act on evidence that no single detection could justify.

010356090100

Hostile0–9

Auto-banning on score alone is off by default. You decide what happens here.

Restricted10–34

Entity creation and event rates are tightened for this player.

Watch35–59

Every action the player takes is recorded in full detail.

Normal60–89

The resting state of a healthy player.

Trusted90–100

Nothing is tightened. The player is invisible to the system.

Everyone starts at 100

A new connection is trusted until it earns otherwise. Nobody has to prove anything to play.

Repeat hits escalate

The same detection tripped again inside a session adds 35% of its penalty each time, and the multiplier stops at 3.1× after six repeats. A cheat that trips one check fifty times converges on a ban; a single noisy hit does not.

Risk-graded penalties

A detection graded medium false-positive risk costs 75% of its penalty; high risk costs 40%. Uncertainty is priced in rather than argued about afterwards.

Recovers at 2 points an hour

Clean play returns points at a rate you set, and the score never climbs past 100. A bad night is not a permanent record.

Watch below 60

Full-detail recording switches on so that when the next hit lands, the evidence is already there.

Restrict below 35

Spawn and event rate limits tighten for that player alone — the rest of the server is untouched.

What a confirmed hit costs

Before escalation and risk grading.

Severity	Checks	Points
Critical	30	−100
High	35	−40
Medium	17	−18
Low	5	−8
Info	1	−3

Resource API

Teach it what your scripts are allowed to do.

Most false positives are a script doing something legitimate that looks exactly like a cheat. Rather than blinding the anti-cheat, tell it what is about to happen — one line, server-side Lua, no framework assumptions.

Authorise, do not ignore

Before your script does something a cheater could also do, say so. The grant expires on its own, so the hole closes even if your script crashes mid-way.

Route your own logic through the pipeline

reportPlayer hands your anti-exploit checks the same thresholds, Integrity Score, panel history, Discord alerts and ban decision the built-in detections get.

Protect your events

Mark any of your server events as server-to-server only. A client that triggers one is flagged instantly, and block also cancels the call.

Everything the panel can do, over HTTPS

Bans, players, detections and live commands are all available with an API key you create in the panel. Webhooks push ban.created, ban.removed and detection.raised the other way, HMAC-signed.

server.lua

-- duration is seconds; -1 (the default) is permanent.
local banId = exports['argus']:banPlayer(source, 'Duping money', { item = 'cash' }, -1)

exports['argus']:kickPlayer(source, 'AFK in a restricted zone')

-- Lift a ban by the public code the player was shown.
exports['argus']:unbanPlayer('AR-7K3QPX', 'appealed and accepted', 'AdminName')

local exists, ban = exports['argus']:getBanInfo('AR-7K3QPX')

Seen enough?

Five minutes from now your server could be running all of it.

Protect my server