Installation · Argus Docs

Requirements

A FiveM or RedM server on a current artefact. Argus declares fx_version 'cerulean'.
OneSync enabled. Every server-side detection reads entity positions, health and weapons off the server, and those only exist with OneSync. It is the default on current artefacts.
A licence. Apply for access on arguss.ac; approved keys appear in the panel.
No other anti-cheat running at the same time. Two at once produce false positives in both, and Argus refuses to start beside one by default.

Install

Download the resource
Sign in to the panel, open your server, and use Download. The archive is built for your licence; unzip it into your resources folder so the folder is called argus.
text
```
resources/
  [core]/
  [scripts]/
  argus/          ← this folder, exactly this name
    fxmanifest.lua
    config.lua
    ...
```
The folder name matters: other resources reference it as @argus once they are integrated. If you must rename it, set the argus_resource convar to the new name.
Add your licence key
Either in server.cfg, which keeps the key out of the resource folder:
server.cfgcfg
```
set argus_license "ARG-PL-XXXXX-XXXXX-XXXXX-XXXX"
```
or in config.lua as Config.LicenseKey. The convar wins if both are set. The key is the one shown on your server's page in the panel.
Grant permissions
Argus uses FiveM's ACE system. Grant the command permission to whoever should run argus commands in chat or the F8 console, and the admin permission to whoever may reconfigure or uninstall it.
server.cfgcfg
```
add_ace group.admin argus.commands allow
add_ace group.admin argus.admin allow
```
You do not need to grant argus.bypass to your staff. Argus tells staff actions apart from cheating on its own in almost every case; see Permissions for when bypass is the right tool.
Start it
server.cfgcfg
```
ensure argus
```
Place it early — before your framework is fine, and before any resource you want protected is ideal, though the integration copes with either order. Restart the server.
Check the banner
After every resource has loaded, Argus prints its banner last so it is not lost under the usual wall of start-up lines. It shows the version, the mode and whether the panel is reachable. In chat or the console:
text
```
argus status
→ Argus v1.11.0 · learning · api ok · 42 players · integrity 100
```
Integrate your resources
From the server console (not chat — this rewrites files), run argus install. The first run explains that FiveM sandboxes each resource to its own folder and writes the one line that lifts that:
server.cfg — above ensure arguscfg
```
exec @argus/data/permissions.cfg
```
Restart, run argus install again, and it reports what was integrated. Resource integration covers what that line does and how to take it out.

The first day

A fresh install is in Learning Mode for 24 hours. Every detection runs and every hit is recorded in the panel; nothing is kicked or banned. That is the time to look at the feed, notice a script that trips a detection legitimately, and fix the configuration rather than the player. Learning Mode ends on its own; you can end it early or extend it under Settings.

Updating

When a newer version exists the panel says so, and the server prints it at boot. Download the new archive, replace the folder contents, and restart the resource. Your configuration lives in the panel, so nothing is lost; the only local file worth keeping is config.lua if you edited it. After updating, run argus install once more — newer versions sometimes add to what the integration protects, and the command upgrades what is already there in place.