Skip to content
§12

Plans, Billing & the Hard Stop

How Sculk FiveM licences work, what a key covers, activation on your server, transfers, and refunds.

On this page5 entries

§12.1The anticheat licence

Subscribing to Sculk FiveM issues a standard Sculk licence key (SCULK-XXXX-XXXX-XXXX-XXXX) immediately at checkout. It's delivered on the confirmation page and stays retrievable in your account.

One product, two durations:

  • Monthly — $24.99 AUD, renews every month.
  • Yearly — $99.90 AUD, renews every year.

Both are the same protection; only how long each payment covers differs. Subscriptions renew automatically and can be cancelled at any time — your server stays protected until the end of the period you've paid for.

If your renewal payment fails, protection stops — the resource loses its licence at its next heartbeat and says so in the console. Pay the renewal invoice (or resubscribe) and the same key works again on the resource's next activation attempt, within five minutes.

Older one-time licences. Sculk was previously sold as a one-time purchase (FiveM Server, and a FiveM Network tier). Every one of those keys is grandfathered: it never expires, keeps exactly what it covered, and nothing about it needs renewing.

§12.2Activation

Download the server-side resource from your account, drop it into resources/ as sculkanticheat, and set the convars in server.cfg (before the ensure — the file runs top to bottom):

# Mandatory: read-only once the server is running, and the resource will
# not start without it.
set onesync on

# `set`, not `setr` — the key must never replicate to clients.
set sculk_license "SCULK-XXXX-XXXX-XXXX-XXXX"

ensure sculkanticheat

The resource reads the key from the sculk_license convar and nowhere else; there is no field inside the resource config to paste it into. The full first-run sequence, including the engine hardening convars, is in Licence Delivery and Activation.

Activation binds a subscription licence to your server's generated identity; the binding is resettable from your account page if you migrate machines. Grandfathered FiveM Network licences activate any number of servers. Each licence holds one live session per server — if a second copy of your key activates somewhere else, your console says so.

Enforcement settings live on the anticheat dashboard and reach every activated server on its next heartbeat — within a minute, no restart.

§12.3What the licence switches on

From resource 3.8.0, Sculk only acts on a server with an active licence. Activation hands your server a licence lease: a short statement signed by Sculk for your server's identity and your key, renewed by every heartbeat and cached in the resource folder (.sculk_lease).

  • With a lease, detections kick, ban, block and refuse exactly as configured. sculk in the console prints protection: ENFORCING.
  • Without one — no key, a wrong or revoked key, a lapsed subscription, or a licence bound to another server — every detection still runs and logs [unlicensed] … NOT enforced, but nothing acts on a player. sculk prints protection: NOT ENFORCING and the reason.
  • If Sculk's website is down, your server keeps enforcing from the cached lease for up to 72 hours, including across restarts. Our downtime does not switch your protection off.
  • Your key never leaves your server. Activation proves you hold it by answering a one-time challenge, so the key is not readable on the network even though FXServer does not verify TLS certificates.

Keep the resource folder writable so the lease can be cached, and leave sculk_api_url unset — only the real Sculk API can issue a lease.

§12.4Transfers and ownership

The licence belongs to the purchase email. To move it to a new server, reset the binding in your account. To transfer ownership to a different person or organisation, open a billing ticket at /fivem/support from the purchasing address.

§12.5Refunds

Refunds are handled under the refund terms in the Terms of Service, plus your rights under the Australian Consumer Law. To start one, open a ticket at /fivem/support with the billing topic and your order id.