Diagnose QBCore resource load order

Start database and framework dependencies before the resources that call them. Use manifests and the first startup error to derive the order; do not copy an arbitrary flat list.

Evidence to collect

• The first error after a clean server start, including resource and file name
• Relevant ensure lines and bracketed groups from server.cfg
• Each affected fxmanifest.lua, including dependency declarations
• The exact deployed commit for every resource in the dependency chain

Diagnostic

1. Run refresh, then ensure the first failing resource and read the first error.
2. If an export is missing, confirm the provider is started and the export exists at the deployed commit.
3. Inspect manifest dependencies. For example, current qb-core declares oxmysql.
4. Expand group folders such as [qb], [standalone], and [voice]; the group name does not prove that one resource inside it starts before another.
5. Compare the generated server.cfg with the pinned recipe before moving lines.

The current official recipe ensures qb-core, then the [qb], [standalone], [voice], and [defaultmaps] groups. Individual resources can still need explicit ordering within those groups.

Fix and verify

Move or add only the provider needed by the first failure. Restart from a clean process, verify all required resources report started, then test the affected user flow and inspect the console again.

Rollback

Restore the previous server.cfg and commit set. If an update included SQL, restore the matching database backup rather than mixing old code with a new schema.

Sources

• Official txAdmin recipe 
• qb-core manifest