Support · Troubleshooting
Fix the install, in order.
Most first-start failures are load order, not bugs. Get the ensure order right, and never edit an escrowed file. When an error is specific, run the Install Concierge for a doc-cited read.
server.cfg loads top to bottom. Everything a resource needs must be ensured above it.
oxmysql → ox_lib → framework → vf_core → vf_* products
attempt to index a nil value (global 'MySQL') · No such export query in resource oxmysql
oxmysql started after a resource that queries the database (or oxmysql failed to start). Put `ensure oxmysql` above every DB-using resource. If oxmysql itself failed, read its own boot lines just above the error.
Failed to load resource / could not find dependency vf_core
A Vice Drip product loaded before the ForgeCore bridge it runs on. `ensure vf_core` must come before any `vf_*` product, and after the framework.
Framework object is nil / QBX/QBCore/ESX not found
The framework loaded after the product that needs it. The framework (`qbx_core`, `qb-core`, or `es_extended`) belongs above vf_core and the products.
Editing an escrowed file breaks the resource / asset failed verification
Only open config and locale files are editable. Editing an escrowed (encrypted) file breaks Cfx asset-escrow verification and forces a re-download. Change config, never core.
Never edit an escrowed file
Only open config and locale files are editable. Editing the encrypted core breaks Cfx asset-escrow verification and requires a re-download — fix load order and config instead.