Updated 2026-10-02 · 2 min read
Intermediate QBCore Tutorials
Start here after you can run a QBCore test server and load a small Lua resource. Choose a task below; there is no requirement to finish every beginner guide first.
Core Development Skills
Create a job
Define a job, then check its grades and how players receive it.
NUI form with a callback
Connect a browser form to Lua and trace the request to server-side validation.
QBCore scripting
Review resource files, the manifest, and callbacks when an integration does not load.
Core functions
Look up a helper before adding your own implementation.
Advanced Features
Use player data to understand jobs, money, and metadata. Read the events reference alongside the handler you are changing, rather than treating an event name as evidence of what it does.
Before changing persistence, inspect the core database schema and your installed resource's queries. For errors, follow the debugging guide and capture the first relevant console message.
Integration & APIs
A working interface is only part of an integration. Review safe server events for payload validation and authorization. Use development practices for resource organization and performance tuning to investigate expensive work. The server optimization guide covers deployment-level investigation.
Prerequisites Review
Keep a test server, the resource's source, and a database backup available. For NUI work, you will also need to read HTML and JavaScript. Record your qb-core revision and any inventory, targeting, or UI dependencies; a tutorial example is not proof that a replacement resource implements the same interface.
Learning Path Recommendations
Path 1: Job & Economy Focus
Read create a job, then set a player's job. Check the result in player data. Test both allowed and rejected grades or roles before adding money or inventory changes.
Path 2: User Interface Focus
Follow the NUI form tutorial. Test a valid submission, an empty payload, an unexpected value, repeated submissions, and closing the interface. Check both the browser and resource consoles.
Path 3: Integration Focus
Use resource debugging to trace one request through its client handler, server handler, and dependency. Reproduce the failure before changing the implementation, then repeat the same test afterward.
Project Ideas
Extend one existing feature rather than replacing a whole system: add a job grade, add a validated form field, or handle a missing-player result in a callback. Keep the change small enough that you can explain the request, permission check, and stored result.
Community & Resources
Use support to report an error in these guides. For an upstream resource bug, include the resource revision, reproduction steps, and a redacted error log in the appropriate project's issue tracker.
Next Steps
Advanced tutorials cover profiling, event review, and upgrades. Return to beginner tutorials for resource structure, or all tutorials to choose another task.
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.
