Rollout Planning

A good anticheat rollout is boring: nothing bans anyone until staff have watched real traffic and agreed the policy is right. This guide is the sequence we recommend for every community, from a 30-slot roleplay server to a multi-server network.

The four stages

1 · Inventory sensitive actions

Before any tooling, list what actually needs protecting. Get the people who built your resources in a room (or a Discord thread) and write down:

• Money events — anything that credits cash, bank balance, or items of value. Include admin/give commands.
• Inventory events — item grants, transfers, crafting outputs, shop purchases.
• Permission-sensitive actions — job changes, whitelist changes, staff commands, vehicle spawning for privileged roles.
• World actions — entity spawns, deletions, explosion triggers, door states, property access.

For each, note which resource owns it and who should legitimately be able to call it. This list is your future policy — the Event Policy Worksheet turns it into rules.

2 · Start in observation

When the build lands, run it in observation mode first: exceptions flow to the incident stream, nothing is blocked, nobody is punished. Give it one to two weeks of real traffic. The goal is to find where your inventory was wrong — the resource nobody remembered, the event that fires oddly during restarts, the legitimate admin tool that looks like abuse.

3 · Set containment rules

Only after observation, decide per policy area what happens on an exception:

• Block — the action is prevented server-side. Reserve this for cases staff validated during observation as unambiguous.
• Flag — the action proceeds, an incident opens, staff review it.
• Review-first — like flag, but the incident is routed to a queue that requires an explicit staff decision.

4 · Review and refine

Policy is never done. Set a monthly habit: read the incident timelines, check what staff overturned, tighten what proved reliable, loosen what generated noise. Evidence beats instinct.

Timeline expectations

Budget roughly: one staff meeting for the inventory, an hour to draft policy, two weeks of observation, then enforcement. Communities that skip straight to enforcement spend the same time anyway — arguing with players about wrong bans instead.

Where support fits

Founding licence holders can open a rollout ticket any time — FiveM support with the "early-access rollout" topic. Bring your inventory list; policy review against it is exactly what that channel is for.