FiveM Knowledge Base

Why this knowledge base exists

FiveM documentation is scattered. The official native reference tells you a function's signature but not what breaks when you call it from the wrong side. Framework functions are documented across three repositories and a Discord. Error messages send you to a five-year-old forum thread where the fix is "nvm fixed it" with no explanation.

Every page here answers the question someone actually had when they searched: what does this do, what does working code look like, and what goes wrong. Each entry carries a runnable Lua example and the pitfalls people hit in practice.

Errors — start here when something is broken

Paste the error into the search and you will usually land on the exact page. Each error entry covers the cause, the fix, and the steps to confirm it worked — not just the message restated. Common ones include attempt to index a nil value, event was not safe for net and could not find dependency.

Natives — with examples, not just signatures

The native pages cover what a function returns, which side it runs on, and a copy-paste example. Client and server natives behave differently, and calling one from the wrong side is a frequent source of silent failure — our client vs server guide explains the split.

Framework API — QBCore, ESX and ox

Framework functions are where most server code actually lives: getting a player, moving money, setting a job, giving an item. Each entry names the framework and the side it runs on, because the same conceptual operation has a different signature in QBCore than in ESX.

Script directory — what the community runs

Reference pages for the resources most servers have installed — ox_inventory, ox_target, es_extended — covering what each does, which frameworks it supports, and what it commonly conflicts with.