Updated 2026-10-02 · 2 min read
Beginner QBCore Tutorials
These guides introduce QBCore resource development. Start with setup if you do not have a test server; start with resource structure if your server already runs.
🚀 Start Here - Essential Tutorials
Create a QBCore server with Docker
Run FXServer and MariaDB with Docker Compose, deploy the QBCore recipe, and verify character persistence.
FiveM development with QBCore
Work through server setup and the structure of a first resource.
Lua scripting for FiveM
Read Lua examples in the context of FiveM resources, natives, and events.
Getting Started Path
- Run a test server. Follow the QBCore quickstart, the Docker Compose server tutorial, or the installation guides. Confirm that you can connect before changing resources.
- Understand the files. Read QBCore architecture and the getting-started guide.
- Load a small resource. Use the scripting guide to work with the manifest and client/server files. Check the console when the resource starts.
- Make one change. Change a message or configuration value, restart the resource as required, and confirm that the result matches your expectation.
Essential Concepts
| Question | Reference |
|---|---|
| Where are a character's job, money, and metadata stored? | Player data |
| Which side receives an event? | Events |
| What does the database contain? | Core database schema |
| How do I investigate a resource error? | Debugging and testing |
Prerequisites
You should recognize variables, functions, tables, and loops. Use the Lua guide above when syntax is unfamiliar. Keep a text editor and a separate development server available; the installation guides list the server prerequisites.
Check each guide's source notes and the versions you installed. Different revisions and replacement resources can expose different configuration fields or APIs.
Common Beginner Mistakes
Keep backups before changing files or importing SQL. Do not use a live server as your first test environment. Read the first console error before treating every later error as a separate problem.
Put custom behavior in a separate resource when possible. For anything that changes money, items, or permissions, read safe server events before accepting values from a client.
Next Steps
Once a small resource loads and you can explain its client/server flow, move to intermediate tutorials for jobs and NUI. Use advanced tutorials when you have a profiling, security-review, or upgrade task. The tutorial directory lists the other starting points.
Support & Community
Use support for documentation corrections and community channels to find the appropriate upstream project. When asking for help, include the resource name, revision, reproduction steps, and the relevant error text. Remove credentials, license keys, and private player data from logs.
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.
