Iconix StudiosDocs

Product documentation

Advanced Vehicle Access System

Install and configure Iconix Vehicle Keys for ownership, shared keys, lockpicking, hotwiring, alarms, job access, and vehicle access validation.

QBCoreESX LegacyQbox
Version1.x
Dependenciesox_lib or configured UI dependency, inventory adapter, vehicle ownership table
SupportDocumentation + Discord
Open Tebex package Ask on Discord

Overview

Vehicle Keys provides a server-authoritative access layer for owned vehicles, temporary keys, NPC vehicles, job fleets, and theft gameplay.

Use this resource as the single source of truth for vehicle access.

Connect garage, dealership, impound, and inventory resources through documented adapters.

Installation

Install dependencies first, then start the Iconix resource after your framework and inventory.

  1. Download the purchased asset from the official Tebex/Cfx.re delivery flow.
  2. Place the resource in your server resources folder using the documented folder name.
  3. Install required dependencies before starting the Iconix resource.
  4. Add the resource to server.cfg after dependencies and before dependent custom scripts.
  5. Restart the server or resource on a staging server and review client/server console output.
ensure ox_lib
ensure your_inventory
ensure iconix-vehiclekeys

Configuration

Review framework, inventory, notifications, lockpick behavior, alarms, job vehicles, and ownership settings before production.

Config.Framework = "qbcore" -- qbcore, esx, qbox
Config.Inventory = "ox_inventory"
Config.Lockpick.Enabled = true
Config.Hotwire.Enabled = true
Config.JobVehicles.RequireJob = true

Always test on a staging server before production.

Back up the database before installing persistent systems.

Keep license keys, database credentials, and player data out of public support messages.

Testing checklist

Validate the full vehicle lifecycle with multiple players before release.

  1. Create or buy a vehicle and confirm owner keys are granted.
  2. Share keys with a second player, then revoke them.
  3. Restart the resource and confirm persisted access still works.
  4. Test lockpicking, police alerts, job vehicles, and garage retrieval.
  5. Review server logs for denied access and failed ownership lookups.

FAQ

Common questions

Does Vehicle Keys support QBCore, ESX, and Qbox?

Yes. Exact framework behavior depends on your selected adapter and installed dependencies.

Can players share keys?

Yes. Shared and temporary key behavior can be configured by the server owner.

Should I install this directly on production?

No. Test ownership, garage, inventory, and restart flows on staging first.

Ready to install Vehicle Keys?

Review the installation checklist, test on staging, then purchase or open a support ticket if your framework stack needs confirmation.