FiveM Start Order Checker
Paste the ensure/start lines from your server.cfg and this tool checks them for duplicate entries, commented-out lines that are silently being ignored, and orderings that commonly cause a resource to fail against a short, named list of known prerequisites — oxmysql, ox_lib, a framework core, and vf_core.
This runs 100% client-side. Nothing you paste is transmitted anywhere, logged, or stored — the analysis is plain JavaScript running in your browser tab, and it works the same with your Wi-Fi turned off.
You can paste the whole server.cfg — lines that are not ensure or start directives are simply ignored. Nothing here leaves this page: there is no fetch, no upload, no server. Open your browser's network tab if you want to confirm that yourself.
Findings appear here
Paste your start lines and click Analyse. You get a line-numbered list of duplicate entries, commented-out lines, and orderings that commonly cause a resource to fail, checked against a short, named list of known prerequisites — not a full dependency graph of every FiveM resource.
What this checks, and what it does not.
What it does
- Parses ensure/start lines you paste and lists them in the order the server would actually process them.
- Flags a small, named set of known prerequisite relationships (oxmysql, ox_lib, the three framework cores, vf_core) when a likely dependent starts first.
- Flags duplicate resource entries and commented-out lines so nothing is silently ignored without you noticing.
What it does NOT do
- Does not read your actual resource folders, fxmanifest files, or convars — only the text you paste.
- Does not know about resources started from a separate exec'd config file it was never shown.
- Does not know every resource's real dependencies — only a small, named list of well-known ones.
- Does not guarantee your server will start cleanly even with zero findings.
Four steps.
- 01
Open your server.cfg and copy the lines you want checked. You can copy the whole file — anything that isn't an ensure or start directive is ignored.
- 02
Paste it into the box above.
- 03
Click Analyse. Findings are listed in line-number order, each tagged error, warning, or info.
- 04
Fix errors first, then warnings, then re-paste and re-check. Info findings are context, not necessarily problems — read the explanation for each one.
Most "it won't start" errors are order, not code.
FXServer works through server.cfg largely top to bottom. A resource that queries a database before oxmysql is ready, or that calls a framework export before the framework core has registered it, typically fails on its very first tick — and the resulting console error usually names the symptom (a nil export, a missing table) rather than the actual cause (the wrong line order). Reordering two ensure lines fixes more "broken" resources than any code change does. The convention — a database connector, then a framework core, then shared libraries, then the resources that depend on them — is the same one described in how to install a FiveM script.
If you already have a specific console error rather than a config you want checked up-front, read why FiveM resources fail to start or how to fix a FiveM resource start order for the failure-mode detail this tool's findings summarize.
Before you rely on this tool.
What exactly does this tool check?
It parses ensure/start lines you paste and checks them against a short, named list of known prerequisite relationships — oxmysql and ox_lib before the resources that commonly need them, each framework core (qbx_core, qb-core, es_extended) before resources named in its family, and vf_core before other vf_ resources. It also flags duplicate resource entries and commented-out ensure/start lines. It is not a full dependency graph of every FiveM resource in existence.
Why did it flag something that actually works fine on my server?
The checks here are heuristics over resource names and text, not a read of any resource's real fxmanifest.lua. Some resources bind lazily and tolerate being started out of the textbook order; some name patterns are coincidental. Treat every finding as something worth inspecting, not a guaranteed bug — and treat a clean result the same way: no findings does not certify your server will boot without errors.
It says a prerequisite was 'not found' — does that mean my server is broken?
No. It means that resource was not present in the text you pasted. If you only pasted part of your server.cfg, or you exec a separate file for your database and library resources, this tool has no way to see that — it can only reason about what you gave it. Paste the full file if you want the check to be more complete.
Is anything I paste here sent to Vice Drip or anyone else?
No. This tool runs entirely in your browser using plain JavaScript string parsing — there is no fetch call, no upload, and nothing is logged or stored. You can open your browser's network tab while using it to confirm nothing leaves the page.
Does a clean result mean my server will start?
No. This tool cannot see your actual resources, their manifests, your database, or your hardware. It only checks ordering against a short, named list of patterns. Your server console remains the authoritative source of truth — this tool exists to catch the ordering mistakes that produce confusing console errors, not to replace reading them.
Two more browser-only tools live in the same place: the resmon total & frame budget calculator and the config & log redaction checker. For a doc-grounded read of an actual error message, try Install Concierge. Back to the tools hub.
This tool checks text against a short, named list of patterns. It does not read your server, your resources, or your database, and a clean result is not a guarantee of anything. It is a utility, not a Vice Drip product claim.
Last verified: 2026-09-02