Introducing FiveBan

If you run a FiveM server, you've probably seen this loop: a player gets banned, a week later they're back on a fresh Discord and a fresh license hash, and your moderators waste another evening figuring out it's the same person. Multiplied across all the servers in our scene, that's thousands of staff-hours per month.

FiveBan is our attempt to break that loop.

What it is

FiveBan is three things in one:

1. A public blacklist database — Discord IDs (and license hashes where available) of confirmed FiveM cheaters, with a public lookup at /lookup and a JSON API at /api/v1/check.
2. A cross-server intel feed — our selfbot watches a curated list of cheating Discords (yes, the ones where bypasses get sold) and links chatter back to player profiles. When the same handle shows up trying to buy a "FiveM bypass" on Tuesday and joins your server on Friday, we already know.
3. A FiveM resource — drop it into your server, plug in the API key, and confirmed cheaters get auto-kicked at connect. No moderation action needed for the easy 80 % of cases.

What it isn't

• An anti-cheat. We don't run on the client. If a cheater has a fresh account, fresh license, no public footprint, and behaves cleanly enough on first session, we won't catch them — that's what your in-game anti-cheat is for. We catch the recidivists.
• A vigilante project. Every confirmed entry has a paper trail: at least one piece of evidence (clip, screenshot, ticket transcript) and a staff signature. Appeals are public and processed.
• Pay-to-play. The lookup is free. The API has a generous free tier. Plans get you higher rate limits, webhooks, and the FiveM resource with auto-update — but the data is the same.

How submission works

Anyone can /submitcheater in our Discord. Reports go through a staff review with the suspect's evidence, license hash, and any cross-server context our selfbot found. Staff vote, evidence is archived, the player is moved from clean → suspicious → confirmed.

A confirmed ban can always be appealed — see /docs/appeals.

What's next

• Webhook support for partner servers (already shipped, this very week).
• A self-service dashboard for plan owners (in progress).
• A leaderboard of servers actually doing the moderation work (open /leaderboard to see how it's going — kudos to RP Vysočina sitting on top right now).

Got a use case we're missing? Open a ticket. We're a small team but the backlog is public — see /changelog for what we're shipping.