SCULK / FIVEM EDITION
Sculk FiveM brings server-side event policy, entity integrity, resource trust, and player-state signals into a single staff-ready incident trail. It is built for decisions you can inspect, not unexplained automatic punishments.
WORKS AT THE EVENT LAYER OF ANY FRAMEWORK · ESX & QBCORE ARE THE REFERENCE TEST ENVIRONMENTS · PLAYERS INSTALL NOTHING
PROTECTION MODEL
Sculk FiveM is designed to make the important context available when staff need it: what happened, which policy applied, and what happened next.
01 / EVENT BOUNDARY
Watch privileged event calls at the boundary, compare payloads to the policy you set, and leave staff with a readable trail when a request falls outside it.
02 / WORLD INTEGRITY
Group unusual spawns, destructive actions, and ownership changes into one case so staff can understand the sequence before deciding what to do next.
03 / PLAYER STATE
Surface impossible state changes, aim anomalies, and movement conflicts beside their surrounding server context instead of judging a player from one isolated sample.
04 / RESOURCE TRUST
Track resource readiness and protected flow expectations so tampering attempts become reviewable evidence rather than silent blind spots.
CHECK SURFACES
The FiveM edition is a model of coverage, not a promise of invisible magic. These are the places your configuration can define normal behavior and escalate the exceptions.
EVENT
POLICY SETExpected call paths, authority checks, and payload rules at the places your server makes consequential decisions.
WORLD
POLICY SETContext around spawned objects, vehicles, peds, explosions, and other world changes that need an owner and a reason.
STATE
POLICY SETMovement, weapons, health, and targeting cues presented as a staff decision aid, not a black-box verdict.
TRY THE MODEL
Three example cases, one per check surface. Read the evidence the way your staff would, then reveal the call. This is a concept preview with example data — the honest version of a "live demo" for a product still in early access.
INCIDENT QUEUE · CONCEPT PREVIEW
EXAMPLE DATA — ILLUSTRATES THE REVIEW MODEL, NOT LIVE PRODUCT OUTPUT
POLICY: amount 1..10,000 · requires open session · max 6/min
bank:withdraw for 250,000 — 25× the payload ceiling, no open bank session in the last 5 minutes.
Same client fired shop:buy 41 times in the prior minute. Both events attach to one case.
Policy for money events is BLOCK after observation — the withdrawal never executes.
Case lands in the staff queue with payloads, sequence, and rate context attached.
STAFF DECISION
Read the timeline, then make the call the way your staff would. The point of the model: by the time a human decides, the evidence is already assembled.
EARLY ACCESS
Buy now and you get a founding licence key instantly at a locked price, the rollout guides, and priority support. The FiveM build itself ships to licence holders when the early-access rollout opens — that part is still in development, and we say so.
Every protection capability is in both tiers. Network adds scale — more servers, shared policy, cross-server review — never safety. We don't sell better detection to bigger wallets.
MOST SERVERS START HERE
Founding licence for a single FiveM server.
$24.99 AUDper server, one-time — early access
One founding licence across your communities.
$59.99 AUDper network, one-time — early access
Your founding key is issued instantly — on screen, by email, and in your account.
Use the rollout guides and priority support to get policy and staff workflow ready.
When the build ships you're emailed first. The same key activates it. Nothing to buy again.
EARLY ACCESS DISCLOSURE: the licence key is issued immediately; the FiveM build is delivered when the rollout ships, with no published date. Founding keys activate the build at no further cost. Full refund any time before your build ships — no questions asked. Not ready for that? Wait for the public release — no hard feelings.
ROADMAP
No dates — dates we can't stand behind are marketing, not a roadmap. This is the order of operations, and founding licence holders are emailed at every step.
Founding licences on sale, rollout guides published, policy support open. Everything sold today is described on this page — nothing more.
The server-side build ships to founding licence holders in observation mode: incidents stream, nothing punishes, staff validate policy on real traffic.
Block / flag / review-first enforcement per policy, ban-identifier import from your previous anticheat, and the staff incident queue hardened by feedback.
Public pricing, network features across communities, and measured benchmark methodology published — the same numbers-or-nothing rule as our Minecraft edition.
DOCUMENTATION PATH
A sensible anti-cheat rollout begins with what your staff can explain. The FiveM docs are organized around setup, observation, and review - then enforcement where you explicitly choose it.
Read the rollout guidesList events, resources, roles, and world actions that deserve a policy.
Send exceptions to the incident stream and let staff validate the context.
Choose which cases should be blocked, which should flag, and which require review.
Use case timelines to adjust policy with evidence instead of guessing.
STAFF GUIDES
Map which server events move money, inventory, permissions, or world state before you write their policy.
Set a consistent staff response for unexpected vehicles, peds, objects, and explosive events.
Choose which signals alert staff, which contain an action, and which need a second look before punishment.
FIVEM SUPPORT
Tell us how your FiveM community handles staff review, protected events, and risky world actions. The right anti-cheat setup starts there.