Skip to main content
Solutions to common setup and usage questions.
Make sure you are on the latest update (1.2.0+). This version adds a dedicated spawn path for vehicles in garage state and improves plate matching consistency. After updating, do a full resource restart.
That is expected if no mileage provider is detected. vPark now auto-hides mileage when no supported script is running.Check Config.Mileage in config.lua:
  • mode = "auto" to auto-detect known mileage resources
  • mode = "manual" to force your own resource + export
Auto-detect currently supports:
  • jg-advancedmileage
  • jg-adavancedmileage (typo-safe fallback)
  • jg-vehiclemileage
You can also use custom scripts via manual mode.
Set Config.Framework = "auto" (or explicitly set esx, qb, or qbx) and ensure framework resources start before vPark in server.cfg.Recommended order:
  1. framework/core resources
  2. dependencies (ox_lib, oxmysql)
  3. worry_vpark
No. Money handling uses your framework/core, not inventory. Config.Inventory is for compatibility/helper item checks (VparkInventory) and future integration use.
Use command: /v listOr from another client resource: exports.worry_vpark:OpenList()
Common causes:
  • You are not in the vehicle.
  • You are too far from your owned parking spot.
  • Vehicle ownership check failed for your framework table.
  • Spot is already occupied.
Use a clean restart cycle:
  1. stop worry_vpark
  2. ensure worry_vpark
Avoid rapid hot-reload while actively in the menu/flow.
Most config changes require a resource restart (and sometimes full server restart if dependency/start order changed). After restart, re-open /v list to refresh menu payload.
Collect these before asking for support:
  • framework type (esx, qb, qbx, standalone)
  • current vPark version
  • relevant server/client console logs
  • your Config.Framework, Config.Inventory, Config.Mileage settings
  • reproduction steps
Please reach out to us on Discord or at support@gdinc.dev with the details above and we’ll do what we can to help!
When working with, testing, or tweaking this resource, do not use a simple restart. To properly restart: first stop worry_vpark, then ensure worry_vpark. Failure to do so can cause issues, errors, and unexpected behavior.