Resourcery

FiveM server development course — learn to run a server, hands-on

Resourcery is a gamified, hands-on course — first 3 phases free for people who want to actually run and manage a FiveM server rather than just download one. It is management-first: you learn just enough Lua to read and configure resources, then spend your time where the real work is — installing and managing scripts, taming the database, wiring events and items, balancing weapons, and moving fluently between the QBCore and Qbox frameworks. Progress saves in your browser; there is nothing to install.

What you'll learn

FXServer and server.cfg, fxmanifest and load order, ensure/start/stop, escrow resources, QBCore vs Qbox, the compatibility bridge (provide 'qb-core'), ox_lib, events and exports, server-side security, oxmysql and prepared statements, ox_inventory items and consumables, weapons and weapon-meta, jobs and the server economy, OneSync, state bags and entity ownership, target systems and stashes, reading the console, resmon and crash dumps, and shipping a change to a live server with txAdmin.

Course outline (16 phases + certification exam)

1. FiveM Foundations — what FXServer is, resources, server.cfg, fxmanifest, load order, and the two build numbers.
2. Installing & Managing Scripts — bracket folders, ensure/stop, escrow resources, and updating without losing your config.
3. Staying Live: Cfx & Rockstar Compliance — the Creator PLA, what you may and may not sell, no-pay-to-win and no-cash-out rules, IP/trademark limits, and the disclaimer your store must carry.
4. QBCore vs Qbox — the shared-object pattern, the compatibility bridge, and the migration map.
5. ox_lib & the Bridge Layer — the toolkit the modern stack runs on and how bridges pick their backends.
6. Events & Exports — the client/server boundary, never trusting the client, and lib.callback.
7. The Database Layer — oxmysql, prepared statements, schema changes and backups.
8. Items, Inventory & Consumables — the ox_inventory item contract, status, consume vs close, and metadata.
9. Weapons — weapons as items, durability vs damage, and weapon-meta overrides.
10. Jobs, Economy & Player Data — grades, money types, society money and player tables.
11. OneSync, State Bags, Targets & Stashes — entity ownership, replication, and the silent stash.
12. NUI: the browser inside the game — the four wires of a HUD, focus traps, DUI on in-world screens, the memory a page costs, and debugging with CEF devtools.
13. Debugging & Server Management — reading the console, the dep-chase loop, resmon and crash dumps.
14. Putting It Together — the reliable update workflow and converting a script end-to-end.
15. Hosting & Deployment — where a server runs, license keys, artifacts and updates, txAdmin in production, ports and DDoS, backups, and going live.
16. Monetizing with Tebex — the merchant-of-record model, the Cfx exclusivity rule, connecting your server, building packages and deliverables, testing, and getting paid.

Frequently asked questions

Is this FiveM course free?

Yes — it's a free, self-paced course that runs in your browser and saves progress locally.

Do I need to know how to code to run a FiveM server?

No. It teaches just enough Lua to read and configure resources, focusing on installing, configuring and maintaining a server rather than writing scripts from scratch.

What is the difference between QBCore and Qbox?

Qbox is a modern framework derived from QBCore. It favors flat exports and ox_lib, uses ox_target and ox_inventory, and keeps QBCore compatibility through a bridge (provide 'qb-core'). The course covers both and the migration path between them.

Which frameworks does it cover?

QBCore and Qbox, each as its own lane of the same curriculum — covered in depth with hands-on labs and interactive console projects. The shared phases are framework-neutral, so the patterns transfer to any stack.

What does the course cover?

Twelve phases from foundations to shipping a change live, plus a certification exam — including frameworks, the database, items, weapons, jobs, OneSync, and debugging.