FiveM basics

Resource structure, fxmanifest, client/server split, events, exports and debugging for FiveM Lua.

Activation Contract

Load this skill when the user creates or edits any FiveM resource, fxmanifest.lua, client*.lua or server*.lua, asks how client/server, events or exports work, or reports a bug that needs server vs F8 logs.

Hard Rules

• Manifest: fx_version 'cerulean' and game 'gta5' (or 'rdr3' / 'common'); every client-served file goes in files.
• Register networked events with RegisterNetEvent; local-only events use AddEventHandler alone, never RegisterNetEvent.
• Server handlers read the sender from source; broadcast with TriggerClientEvent(event, -1, ...).
• GetInvokingResource() is nil for every net event that crosses the network; it is not an authentication check. Validate types, ranges and server-owned state instead.
• Never handle money or item transactions on the client; validate and apply on the server.
• No game natives in shared_scripts unless guarded by environment.
• Use PlayerPedId() not GetPlayerPed(-1); use #(a - b) not GetDistanceBetweenCoords.
• Prefer local; prefer variable Wait() over fixed Wait(0).
• Resource names use underscores, no spaces or special characters.