client · memory
Cheat menus
Memory scanning catches known menus and the recompiled variants that slip past fixed lists.
4 years in production · since 2021
If it flagged,
it's a cheat.
Your staff stopped reading alerts because 90% of them were nothing. Likizão AC is tuned against your own server base until an alert means something again — and it never costs your players a frame.
21:04:12FLAGJumpyFish8747#150112Shark Menu [10.1]
21:04:14BANJumpyFish8747#150112Shark Menu [10.1]
21:04:15FLAGDustySnaily3526#111321Noclip [15.0]
21:04:18BANDustySnaily3526#111321Noclip [15.0]
21:04:20FLAGNUNES#110638Solo Session [3]
- In production
- 4 years
- False positives
- < 0.1%
- Client cost
- 0.02 ms
- Frameworks
- All
Accuracy
Too many alerts is the same as none
An anti-cheat that fires on lag, on packet loss and on every odd latency spike trains your team to ignore notifications. When the real cheater shows up, nobody is looking.
What you have been living with
- A log channel with hundreds of messages a day
- Legitimate players banned for freezing
- Staff muting the webhook just to get work done
- Generic rules that know nothing about your server
How Likizão works
- Detections confirmed across successive windows before alerting
- Lag and packet loss never turn into punishment
- Rules tuned against your own server base, one by one
- Every alert arrives with the evidence behind the decision
Coverage
Six fronts, checked continuously
Cheating in FiveM does not come from one place. Each front runs where it can be trusted — on the client or on the server — and none of them depend on a fixed signature list.
client · runtime
Lua executors
Any code loaded outside the resource cycle is intercepted before it runs. The executed snippet ships with the ban.
server · runtime
Resource injection
Resources appearing after boot are blocked and compared against your signed server manifest.
server · stability
Crashers
Malformed entities, state floods and the routines that take a whole city down die before they propagate. A new method is blocked within 30 minutes.
server · physics
Impossible movement
Teleport, noclip and off-curve speed are measured against the map collider — and confirmed before anyone is punished.
server · events
Forged events
Network triggers are validated by origin and frequency. Entity spam and remote explosions die on the server.
30 mincrash response ceiling
Response commitment
New crasher? Fixed in 30 minutes, maximum
Taking the city down is the attack that costs you most, so it comes with a deadline. A new crash method shows up on your server and the fix ships within 30 minutes — no queue, no "open a ticket".
Panel
The argument ends at the evidence
Every ban opens a record with what was detected, when, and the material backing the decision. Your team reviews, upholds or reverses it — and the player sees exactly what you see.
- Flagged code snippet or memory region
- The event that triggered the detection, with origin and timestamp
- The player history on your server
- One-click review, with a log of who decided what
No client screenshots, ever
Likizão never captures a player screen. Evidence comes from what happens in the game runtime, not from the private life of whoever is connected.
| Player | Reason | Evidence | When |
|---|---|---|---|
| zK_menu#0917 | Cheat menu | memory dump | 2 min ago |
| ghost__#7731 | Resource injection | manifest + log | 14 min ago |
| r4ge#8890 | Teleport | coordinate trail | 38 min ago |
| vLz_crash#3390 | Entity crasher | event log | 1 h ago |
Already running it
Servers using Likizão AC
Cities in production right now, from Brazil to Spain, the UK and the Middle East.
Lado Leste
Cidade Nobre
Cidade Santa
Brasil RP
Cidade Grande
KNG Estate
Cidade Maresia
Real RP
Liberty 99
Vice City
Malta RP
ZERO1 Roleplay
Cidade Alta RJ
Krown
Orizon RP
Prime RP
Nordeste RP
Fronteira
Pollaca
Goiás Roleplay Season 3
Wanted Bahia
Royal
Atlantis
Alaska RP
Install
We install it, inside your base
This is not a zip you drop into resources and hope. Installation is manual and integrated into your server code — that is what makes detection precise instead of generic.
- 1
Talk on Discord
Framework, slot count, what protection your base already has, and where the problems show up today.
- 2
We study your base
We map your resources and what normal behaviour looks like on your server. Skip this and any anti-cheat becomes a false-positive generator.
- 3
Manual integration
Likizão goes in coupled to your base, with rules tuned to your case. You follow along, approve, and go live.
Compatible with every framework
QBCore, ESX, ox, vRP, qbox or a custom base — Likizão watches the runtime, not your framework. None of your resources need rewriting.
Configuration, permissions and integrations in detail in the documentation.
License
One plan, no monthly fee
A single onboarding fee. No subscription, no per-slot billing, no surprise next month.
Likizão AC license
Onboarding fee
R$ 2,500one-time payment
- Manual installation integrated into your base
- All six detection fronts, tuned to your server
- Ban panel with evidence attached
- Compatible with every framework
- Updates and new detections included
- Support on Discord
Payment methods
- PIX (BRL)
- Cryptocurrency
Dedicated support
Custom quote
For large networks or operations that cannot go down. We treat your server as a single, specific case.
- Support customised for your server
- Response SLA of one hour, maximum
- A private contact channel with the team
- We see the problem through — no ticket handed back
Questions
Before you install
Did not find what you needed? The team answers on Discord, and the documentation covers configuration, permissions and integrations in detail.
How do you keep false positives down?
Physics and network detections require confirmation across successive windows before they alert, so lag and packet loss never punish anyone. Combined with the tuning done against your base during installation, the rate stays under 0.1% — and every ban remains reviewable in the panel.
Does it weigh on the player client?
Client checks run in short slices outside the render frame. Measured cost is around 0.02 ms per tick — less than most HUDs consume. Nobody loses FPS because of the anti-cheat.
Does it work with my framework?
Yes, with any of them. QBCore, ESX, ox, vRP, qbox or a custom base. Likizão watches the server runtime, not the framework, so none of your resources need changing.
Why is installation manual?
Because a generic anti-cheat produces generic alerts. Integrating into your base lets us tune what normal behaviour means on your server — and that is exactly what separates precise detection from notification spam.
A new crasher showed up. How fast do you fix it?
Thirty minutes, maximum. Crashing is the attack that costs you most — it drops the whole city and empties the server — so it carries a hard deadline. You report it on Discord and the fix ships inside that window, with no queue and no escalation.
Do you take screenshots of my players?
No. Likizão never captures the screen of anyone connected. Evidence comes from the game runtime — flagged memory, the triggering event, the coordinate trail — never from a player screen.
Do you detect identifier spoofing?
It is not our focus. We would rather be excellent at what actually takes servers down — menus, executors, resource injection, impossible movement, forged events and crashes — than mediocre at everything. Banning by identifier still works normally in the panel.
How long have you been around?
Four years, since 2021, protecting FiveM servers in production — including roleplay cities with hundreds of concurrent players.
How does payment work?
A single onboarding fee of R$ 2,500, no monthly charge. We accept PIX in Brazilian reais or cryptocurrency. Enterprise is quoted case by case.