Skip to content
SCULKANTICHEAT
Sign up
FiveM documentation§1 Licence Delivery & Activation
  1. 1Licence Delivery & Activation
  2. 2Rollout Planning
  3. 3Event Policy Worksheet
  4. 4ESX, QBCore & Frameworks
  5. 5Entity Incident Playbook
  6. 6Staff Review Workflow
  7. 7Migrating from Another Anticheat
  8. 8Licences & Activation

Elsewhere

§1

Licence Delivery & Activation

What a Sculk FiveM licence includes, how instant delivery works, and how to activate on your server.

On this page6 entries

Buying a Sculk FiveM licence gives you everything you need to protect your server today. Delivery is instant and activation takes a few minutes.

§1.1What you get

  • A licence key, issued instantly at checkout — on the confirmation screen, by email, and in your account. It never needs to be repurchased.
  • The Sculk FiveM resource, downloadable from your account the moment payment succeeds.
  • The setup guides in this documentation section: policy planning, event inventory, entity incident playbooks, and staff review workflows.
  • Priority support. Questions get a tracked ticket and a real reply — see FiveM support.

§1.2Activating on your server

server.cfg runs top to bottom, so every set below has to come before the ensure. Work through this in order and the server comes up protected.

  1. Download the Sculk FiveM resource from your account.

  2. Unzip it into your server's resources folder as a folder named sculkanticheat — that is the name the ensure line uses.

  3. Add this block to server.cfg:

    # Mandatory. Without OneSync the server never parses game state: no entity
# exists server-side, GetPlayerPed returns 0, and most of the resource is
# inert. It is read-only once the server is running, so it has to be set
# here, before start.
set onesync on

# Your licence key, from your account page.
# Use `set`, NOT `setr` — this must never replicate to clients.
set sculk_license "SCULK-XXXX-XXXX-XXXX-XXXX"

ensure sculkanticheat

    There is no prompt inside the resource config for the key: it is read from the sculk_license convar and nowhere else. Start without it and the console says No licence key set.

  4. Exempt your staff before you arm anything:

    add_ace group.admin sculk.bypass allow
add_ace group.admin sculk.spectate allow

    Exempt players still trip detections and still log; they are simply not acted on. That is how you watch what a detection would have done before it does it to a real player.

  5. Set the rest of the engine hardening convars. server.cfg.example ships inside the download with the full block — entity lockdown, request-control filtering, state-bag strict mode, identity trust and the blocked net game events. They prevent whole categories of cheat at the engine level, which is worth more than any detection: a detection notices something after it happened, these stop it happening. The resource checks every one of them at boot and prints which are still leaving a hole open, so you do not have to take this on trust.

  6. Start the server and read the console. sculk prints licence status, version, clients and bans on file. sculk detections lists every detection, the evidence it rests on, and the action it will actually take — anything capped below what you configured is marked, and anything with no implementation behind it is named as not running.

§1.2.1Tune before you enforce

Set the detections you are unsure about to Log on the anticheat dashboard. They record without punishing, and changes reach every activated server on its next heartbeat — within a minute, no restart. Raise them to Warn, Kick or Ban once you have watched what they catch on your own server.

§1.3The protection model, in one paragraph

Sculk FiveM is server-side and policy-first. It watches privileged server events, entity and world changes, resource trust signals, and player state. Anything outside the policy you define becomes an incident with a timeline staff can read: observed, correlated, contained per your rules, and reviewed by humans. Players install nothing, and nothing is punished that your configuration didn't explicitly choose to punish.

§1.4Who a licence is for

Buy a licence if you run a live FiveM community and you want staff-reviewable anticheat rather than a black-box ban bot. Spend a little time up front preparing policy so enforcement lands cleanly.

§1.5Next steps

  1. Read Rollout Planning, the order of operations from install to live enforcement.
  2. Work through the Event Policy Worksheet with whoever knows your server's resources best.
  3. Set up your staff workflow with the Staff Review Workflow guide.
  4. Add the Sculk Discord bot to your community so staff can run lookups, kicks, bans and whitelist changes without leaving Discord. The invite and the /bind step are on your service page in the client area.