Find the right QBCore guide

Choose the task that matches what you are doing now. These independent community guides link to project-maintained sources wherever framework details can change.

Use the documentation search above. Queries such as clear cache, install QBCore on Windows, or qb-inventory lead directly to the relevant guide or section.

Start, verify, or repair a server

Deploy a separate QBCore test profile with the project-maintained txAdmin recipe.

Start a test server

Set up FXServer, txAdmin, database access, networking, and backups before deployment.

Prepare a Windows or Linux host

Check the console, persistence, permissions, and essential resources before customization.

Verify the first boot

Start from symptoms such as connection failures, resource conflicts, or stale client data.

Fix a server problem

Find source-linked setup notes and common fixes for maintained QBCore resources.

Configure a qb-* resource

Compare versions, protect local changes, test on staging, and prepare a rollback.

Plan an update or migration

Operate the server safely

Treat client input as untrusted and keep permissions, state, and value checks server-side.

Secure server events

Establish a repeatable workload, record a baseline, and change one variable at a time.

Measure performance

Use the framework references

Core framework — Core object, player data, shared data, functions, and events
API reference — Client and server functions, events, callbacks, and commands
Practical guides — Focused workflows for common administration and scripting tasks
Database — Core schema context and database boundaries
Development — Local tooling, debugging, performance, and safer implementation practices

Verify changing information

Framework APIs and maintained resources can change after a guide is published. Before applying a command, configuration, or database change to production:

Open the upstream source linked from the guide.
Compare it with the exact commit deployed on your server.
Test the change on a separate profile and database.
Keep a verified backup and rollback path.

Use the official project documentation and the QBCore GitHub organization as the final source of truth for current framework behavior.