Updated 2026-10-02 · 2 min read
Advanced QBCore Tutorials
Use these guides when an existing resource needs investigation or a server change needs a rollback plan. This is a directory of tutorials and API references, not a certification course.
Prerequisites
Work on a test server with a copy of the relevant resources and a database backup. Record the commits or versions you are testing. You should be able to trace a client event to its server handler and read the Lua used by the resource you are changing.
For a first resource, start with beginner tutorials. For jobs and browser interfaces, use the intermediate tutorials.
Framework Mastery
Custom resource development
Structure an extension separately from qb-core so framework updates are easier to review.
Core functions
Find the framework helpers used by an existing resource.
Server functions
Check server-side signatures before changing player state or adding a callback.
Client functions
Check the client API separately; client and server helpers are not interchangeable.
Complex System Development
| Task | Start here | Evidence to collect |
|---|---|---|
| Investigate a hitch or slow resource | Performance tuning, then server optimization | A profile captured while the problem occurs, the resource revision, and the same workload after the change |
| Review a network event | Safe server events | Tests for unauthorized callers, malformed payloads, repeated requests, and disconnected players |
| Change persistent player data | Core database schema | The actual schema, migration script, backup, and a restore test |
| Trace an integration failure | Debugging QBCore resources | The first relevant error, reproduction steps, and the resources involved |
Advanced Development Patterns
Before an upgrade, read breaking changes and resource updates. Change one dependency or resource at a time on staging. Record what changed and how to restore the previous state; a successful startup alone does not test player data, purchases, jobs, or reconnects.
For a failed rollout, use connection troubleshooting to separate connection problems from resource startup failures.
Specialization Areas
The server events and client events references help identify which side owns an operation. Use the resource reference for individual dependencies rather than assuming every resource has the same API.
Moving an existing server from ESX is a separate task. Read the ESX-to-QBCore migration guide before changing framework-specific resources or player records.
Getting Started
Choose one reproducible problem from the table above. Save a baseline, make one change, and repeat the same test. Keep the result with the resource revision so another maintainer can reproduce it.
Navigation
All tutorials · Beginner tutorials · Intermediate tutorials · Report a documentation issue
Found an issue in this guide?
Send the page URL, the affected example, and a source or reproduction to the site maintainer. For a server or resource problem, use the support guide.
