Vice Drip
Real the flow, the copy, the redaction warning, and the entire worked diagnosis on the right — it is the verbatim output of the shipped deterministic engine (SAMPLE DIAGNOSIS — engine is live in code, 63/63 analyzer tests). Demo the pre-filled selections and pasted log — a staged vf_garage case so you can audit the full surface without running the app. The Diagnose button calls the live API only in the app.

Install Concierge

Diagnose your install.

Answer three things, paste the error if you have one, and get a grounded read. Live products get full install and troubleshooting support; products still in development give a pre-purchase compatibility check only. Secrets are stripped before anything is diagnosed — the box warns you, and the server strips again as a floor.

1 · Which product?

Live — full install + troubleshooting support. Escrow: escrowed core, open config.

2 · Your framework

3 · Where are you stuck?

4 · Paste the error (optional but faster)

Before you paste — redact your secrets

Never paste database passwords, your sv_licenseKey, API keys, Discord tokens, or full connection strings. We strip anything that looks like a secret server-side before it is diagnosed, displayed, or stored — but the safest secret is the one that never leaves your server. Paste the error lines, not the whole config.

Upload a log / .cfg / .sql file 2 secret-like value(s) will be stripped before sending.

Diagnosis · TitleLock Garage (vf_garage)

Sample diagnosis — engine is live in code (63/63 tests)

A resource called oxmysql before it started (or oxmysql failed to start).

Likely cause

A resource called oxmysql before it started (or oxmysql failed to start). oxmysql must be ensured before anything that queries the DB.

Fix steps

01Put `ensure oxmysql` above every DB-using resource in server.cfg (order: oxmysql → ox_lib → framework → vf_core → products). If oxmysql itself failed, check its own boot lines just above this error.
02Move `ensure oxmysql` above `ensure vf_garage`. Order at the top should be: oxmysql → ox_lib → framework → vf_core → vf_* products.
03Move `ensure vf_core` above `ensure vf_garage`. Correct order: oxmysql → ox_lib → framework → vf_core → vf_* products.
04Move the framework `ensure qbx_core` above vf_core and the products.
05Move `ensure ox_lib` above `ensure vf_garage`.

Files to check

server.cfg (resource start order)

Correct ensure order — real commands, never invented

ensure oxmysqlensure ox_libensure qbx_coreensure vf_coreensure vf_garage

Do NOT touch

Do not edit the encrypted core of TitleLock Garage (vf_garage) — only its open config and locale files are editable. Editing an escrowed file breaks Cfx asset-escrow verification and requires a re-download.

Don't remove or edit other resources to force this one to load — fix the load order / config instead.

Don't hand-edit database rows to work around the error before the root cause is fixed.

Never paste secrets (DB password, sv_licenseKey, API tokens) into support; rotate anything already shared — the values were redacted before storage.

Confidence High — a specific, grounded match.

Redacted server-side: DB_CONNECTION_STRING ×1 · IP_ADDRESS ×1. If any of these were real, rotate them now.

Sources — every step traces to a real doc

VICE DRIPTitleLock Garage (vf_garage) — product truth
VICE DRIPForgeCore (vf_core) — product truth
VICE DRIPFramework Lock-In: Why Switching Costs More Than Choosing
VENDORoxmysql documentation
VENDORFiveM documentation
VENDORQbox documentation
VENDORox_lib documentation

Did this fix it?

Create a support ticket →

This is a deterministic, doc-grounded read — not a promise your server is working. You confirm what's fixed; we never claim it for you.