TitleLock Garage (vf_garage)
Vehicles should disappear only in the story, never in your database.
Players forgive a crash. They do not forgive losing the car they spent three weeks earning. TitleLock Garage is built around persistence, ownership, impound logic, and transfer records — so vehicles feel like assets, not temporary props.
The short answer
TitleLock Garage is a FiveM garage and vehicle persistence script for roleplay servers. It manages owned vehicles, stored vehicles, impounds, transfers, and restart-safe vehicle state — and it adapts to your framework's existing tables instead of replacing them. Persistence is a claim on our QA gate, not yet a published measurement; its resmon figure reads [MEASURED-PENDING] until a real client produces one.
Trust receipts
01 / 08Performance · measured
Declared support — exact tested versions publish with the release QA matrix.
What you can read · escrow
Ships open
- full config surface (≤20 top-level keys)
- locales
- framework bridge glue
- public exports / API
Ships escrowed
- core logic (Cfx asset escrow)
Exact file-level manifest publishes with the release.
Support · SLA
- First response <24h
- S1 hotfix <12h
- free updates within major version
What it does
02 / 08Real condition persistence: fuel, engine and body health, dirt level, and every cosmetic mod slot captured on store and reapplied on retrieve — not a fresh-spawn reset
Public, job, house and impound garage types, with the house type exposed as an API a housing resource can drive
Shared keys per plate, owner transfers behind proximity and explicit acceptance, and impound release with an escalating daily fee
Two independent checks on every retrieve: a conditional database state transition with affected rows checked, plus a per-plate in-flight lock
Framework-adapter mode: detects and reads/writes Qbox and QBCore's player_vehicles or ESX's owned_vehicles, or runs fully standalone against its own table
Plates are read from the server-side entity, never from a client argument, and ownership is re-checked on every store, retrieve, transfer, key grant and impound release
See it run
03 / 08TitleLock Garage (vf_garage) demo loop — capture pending. Real client footage only; no mockups presented as gameplay.
TitleLock Garage (vf_garage) NUI detail — capture pending. Real client footage only; no mockups presented as gameplay.
Captures come from our own test servers, HUD-off, 1920×1080. We never present concept art or mockups as gameplay.
Compatibility
04 / 08Declared support — exact tested versions publish with the release QA matrix.
Every Vice Drip resource talks to your framework through one open bridge module in VF Core — Qbox/ox_lib first-class, ESX Legacy via bridge, QBCore compat — with no hard framework dependency baked into the product. Swap frameworks; keep your stack.
Requirements
05 / 08- Version
- 1.0.3
- fx_version
- cerulean
- Lua
- 5.4 (lua54 'yes')
- Minimum artifact
- not declared by the manifest
- Same shape as vf_jobs: the manifest names only vf_core, and vehicle persistence runs through vf_core's data layer, which declares oxmysql itself. oxmysql is therefore required and started first, even though this manifest does not name it.
Requirements are read from each resource's own fxmanifest.lua. We do not publish a minimum artifact build because none of our manifests declare one — run a current recommended artifact and Lua 5.4 will be available.
These come from the resource’s own manifest, not from a marketing sheet — the same file your server reads at start. If a dependency is missing, FiveM says so in the console and the resource does not start; nothing half-runs.
Changelog
06 / 08Straight answers
07 / 08Does VF Garage replace my framework's vehicle tables?
No — adapter mode works with your existing framework tables instead of replacing them, which is what makes install and later migration low-risk. A standalone schema is available if you'd rather it own persistence.
What survives a server restart?
Stored vehicles persist with fuel, mods, and condition. Impound state and ownership transfers persist too — restart-proof persistence is the product's core claim and part of its release QA.
Does it handle impound with fees?
Yes — public, job, house, and impound garage types are configurable, including impound fees with escalation rules.
Get it
08 / 08TitleLock Garage (vf_garage)
Escrowed core, open config and bridge — exact manifest at release. First response <24h.
One community per purchase · free updates within the major version · License Terms · Refund Policy
Also in: Starter Bundle · Complete RP Server
Field guides: Qbox vs QBCore vs ESX Legacy in 2026 · How to Vet a FiveM Script Seller Before You Pay · What FiveM Scripts Actually Cost (2026 Price Survey, 13 Stores) · Framework Lock-In · FiveM Garage Script Buyer's Guide (2026) · Best FiveM Scripts in 2026 · Cfx Marketplace vs Tebex vs Direct · FiveM Housing Script Buyer's Guide (2026) · FiveM Real Estate Script Buyer's Guide (2026) · FiveM Resource Start Order · The FiveM Database Layer · Restart Safety · How to Debug a FiveM Script · The FiveM Script Update Checklist · ESX to Qbox Migration