WXMAPSDocs

Impound Job Installation

•5 min read

View Impound Job Script in the WXMAPS store

Impound Job Installation

This gets vs-impoundjob running from a clean download. Do the steps in order.

Keep the folder named vs-impoundjob. The encrypted files are licence-bound to the original folder name, the traffic cone item is wired to the resource-scoped export vs-impoundjob.cone, and other resources reach the script's exports by that name. Renaming the folder breaks all three.

Step 1: Install the dependencies first

Install and start these before the script. See Dependencies for what each one is for.

  • ox_lib, oxmysql, ox_target, ox_inventory
  • vs-npc-dialogue (the free companion resource that runs the conversations with the receptionist, the clerks, and the Public Job dispatcher)
  • Your framework core: es_extended, qbx_core, or qb-core

Step 2: Upload the script

Log in to the Cfx.re portal with the Cfx account you purchased with, open Granted Assets, and download vs-impoundjob. The same purchase also grants vs-impound-heist; set that up afterwards with the Impound Heist installation guide if you want it. Upload the whole vs-impoundjob folder into your resources/ directory. A sub-folder such as resources/[wxmaps] is fine. Do not rename it.

Step 3: Remove the stock tow job

vs-impoundjob declares itself as qbx_towjob and qb-towjob, so it takes the place of those resources. Stop and remove qbx_towjob or qb-towjob if your server runs either. Any resource that lists them as a dependency will start against vs-impoundjob instead.

Step 4: Order server.cfg correctly

Every dependency must start before the script, and the framework core should too.

ensure oxmysql
ensure ox_lib
ensure es_extended        # or qbx_core / qb-core
ensure ox_target
ensure ox_inventory
ensure vs-npc-dialogue
ensure vs-impoundjob

If the framework core starts after the script, it is detected late and the console prints Framework resolved late. That is handled, but the clean order above avoids it. If no core is found at all after 15 seconds, the console warns that it is running standalone. See Compatibility for what that means.

Building your yard inside the Los Santos Impound MLO? Ensure wxmaps_commons and the map before vs-impoundjob.

Step 5: Database

You do not need to import anything. On first start the script creates its 12 tables (all prefixed imp_) itself, and it is safe to restart. install.sql holds the same schema for owners who prefer to provision it by hand:

mysql -u <user> -p <database> < install.sql

A healthy start prints a line per data store, then:

[vs-impoundjob] Server started | Framework: esx | Storage: oxmysql (N stores hydrated)
[vs-impoundjob] Lot accounts: internal (imp_accounts)

If oxmysql is not running, the script refuses to load anything and says so in red. It never runs on empty data.

There is no job SQL to import either. A Player Staffed or Auto Staffed lot creates its own framework job when you build it.

Step 6: Register the items

Add traffic_cone and wheel_chock to ox_inventory. The cone needs its client.export. Copy-paste blocks are on the Items page.

Step 7: Configure the essentials

Open config.lua (the only file you edit) and check:

  • Who may open the Creator. Any one of these lets a player in:
    • the ACE in Config.CreatorAce (group.admin by default);
    • the resource's own ACE in Config.CreatorPermission (vs-impoundjob.creator), which hands out the Creator without full admin;
    • an identifier listed in Config.CreatorIds;
    • a framework admin group listed in Config.AdminGroups.
  • Who counts as police. Config.PoliceJobs (default { 'police' }). Add a sheriff or ranger job here, or in Config.TowTarget.jobs.
  • The assistance-call command. Config.CallCommand.
  • Where lot money is held. Config.LotBank stays 'internal' unless you have set up ESX society accounts. See Dependencies: lot money.
  • Language. Config.Locale ('en').

Config.CallCommand ships as 'chiama' (Italian for "call"). It is the one command every player types to ask a yard for help, so change it to the word your players would use, for example 'calltow', before you go live.

Everything else (fees, ped models, opening hours, wear, Public Job balance) is a runtime setting you edit in-game in the Creator. Those settings are stored in the imp_settings table. See Configuration.

Step 8: Build your first yard

In-game, run /impoundcreator as an admin.

  1. Click + New lot, give it a name, and pick a service mode.
  2. On the Setup tab, place each point the mode asks for. The sidebar shows how many are placed out of how many.
  3. On the Yard bays tab, lay the parking bays the yard holds cars in.

The full walkthrough, including which points each mode needs, is on the Creator page.

At a Player Staffed or Auto Staffed lot, place the clock-in point. Police tows are only offered to a staffed lot when someone is clocked in there, and the clock is the only way to clock in. Without one, a Player Staffed lot never receives a police tow, and an Auto Staffed lot always sends the NPC truck.

Step 9: Test and go live

  1. As an officer, sit in or look at a car and run /requesttow. Pick the yard and give a reason.
  2. Watch it get collected.
  3. As the car's owner, collect it from the receptionist, or from a staff member at the counter.

Confirm Config.Debug = false (the default) before opening to players.

Still stuck? See Troubleshooting & FAQ, the general installation guide, or open a ticket on Discord.

PreviousOverviewNext Dependencies & Compatibility