Car Boosting
Set up tablet-based vehicle theft contracts, driver progression, and police alerts for Qbox.
Car Boosting gives players a tablet full of vehicle contracts. They find the assigned car, bypass its security, remove a tracker when required, and deliver it for money and XP. Higher reputation unlocks tougher classes and larger rewards.
What you need
- OneSync and Qbox (
qbx_core). ox_lib,oxmysql, andox_inventory.qbx_vehiclekeys, with the supplied contract-vehicle compatibility hooks.- A working database connection through
oxmysql.
Keep the resource folder named rw_carboosting. The tablet item calls an export using that name.
Install the resource
- Follow the shared installation steps.
- Merge the entry from
install/items.luainto the returned items table inox_inventory/data/items.lua. Don't replace the whole items file. - Copy
web/images/boosting_tablet.pngintoox_inventory/web/images/so the inventory can display the tablet. - Check that the configured
lockpickandadvancedlockpickitems exist in your inventory setup. - Install the vehicle-key compatibility hooks described below.
- Adjust
shared/config.luaandshared/police.lua, then start the dependencies before the boosting resource.
ensure ox_lib
ensure oxmysql
ensure qbx_core
ensure ox_inventory
ensure qbx_vehiclekeys
ensure rw_carboostingThe server loads install/schema.sql and creates its database tables on startup. Keep that file in the resource. You don't need to manually import it for a normal first install.
Set up vehicle-key compatibility
The supplied install/patch-vehiclekeys.ps1 adds hooks to qbx_vehiclekeys so secured contract cars use the boosting mod's lockpick and hotwire stages. Other vehicles keep the usual key behavior.
On a Windows server, run it against your resources directory:
./install/patch-vehiclekeys.ps1 -ResourcesRoot 'C:/YourServer/resources'The path above is an example—replace it with your server's path. The script expects qbx_vehiclekeys under [qbx]/qbx_vehiclekeys, backs up the files it changes, and stops if it can't find the expected hooks. If your layout or key resource differs, review the patch and adapt those hooks to your installation. Recheck compatibility after updating vehicle keys.
Try your first contract
- Give your test character a Boosting Tablet through your usual inventory administration tools.
- Use the tablet and choose an available contract. New drivers start with class D.
- Travel to the pickup and find the car with the assigned plate.
- Follow the lockpick and hotwire prompts. Remove the tracker if the contract requires it.
- Deliver the assigned car to the revealed drop-off before the contract expires.
Delivery rewards depend on vehicle condition. Body and engine damage lower the payout; a clean delivery can earn a bonus.
Configuration files
| File | What to change |
|---|---|
shared/config.lua | Contract board, classes, locations, tools, timings, and rewards. |
shared/police.lua | Police alert triggers, messages, details, and blips. |
shared/progression.lua | Progression and condition calculations; this is logic rather than the main settings file. |
server/dispatch.lua, client/dispatch.lua | Dispatch adapters when connecting a custom police dispatch system. |
Tune the contracts
| Setting | What it controls |
|---|---|
TabletItem | Inventory item used to open the tablet; default boosting_tablet. Update the inventory entry too if you change it. |
MoneyType | Payout account; default cash. |
BoardSeconds, OffersPerClass | Board refresh period and number of offers per class. |
CooldownSeconds | Contract cooldown. |
MinPolice, PoliceJobs | Police availability requirement and job names. The default minimum is 0. |
Classes | Class names, unlock levels, base rewards, XP, time limits, tracker requirements, and vehicle models. |
LevelThresholds | XP thresholds used to determine driver level. |
Pickups, Dropoffs | Fixed pickup parking positions and delivery locations. |
Access | Lockpick items, skill checks, attempt durations, retry delays, and tool-break chances. |
TrackerSeconds, HackRetrySeconds | Tracker-removal time by class and retry delay. |
TrackerPingSeconds, TrackerBlipSeconds | Frequency and duration of tracker pings. |
MinDeliverySeconds, DeliveryRadius | Minimum delivery time and accepted drop-off distance. |
Condition | Body/engine weighting, minimum payout multiplier, and clean-delivery bonus. |
AccessSounds, DeliveryReceipt | Access audio and delivery-receipt display. |
Default classes
These are base rewards before the vehicle-condition adjustment, not guaranteed payouts.
| Class | Required level | Base reward | XP | Time limit |
|---|---|---|---|---|
| D | 1 | 900 | 75 | 20 minutes |
| C | 3 | 1,800 | 125 | 22 minutes |
| B | 5 | 3,200 | 190 | 25 minutes |
| A | 7 | 5,200 | 280 | 28 minutes |
| S | 9 | 8,000 | 400 | 30 minutes |
| S+ | 12 | 12,000 | 550 | 35 minutes |
Class D has no tracker-removal requirement by default; the remaining classes have one. Check every pickup on your map, especially if you use custom interiors or map replacements.
Police alerts
The default connection is builtin. Failed lockpicks, failed hotwires, and active trackers trigger alerts by default; successful entry and successful hotwiring do not. Cancelling an attempt does not count as a failed attempt.
For a custom dispatch adapter, set Config.PoliceAlerts.connection to custom and implement the adapter in the supplied dispatch files. fallbackToBuiltin controls whether built-in alerts are used if that adapter fails.
If something isn't working
The tablet doesn't open: check the inventory item name, client export, resource name, and start order. Restart inventory after changing its item table.
A contract car receives keys too early: recheck the vehicle-key hooks. Secured contract cars should go through the boosting mod's access stages.
No contracts are available: check your driver's level, the police requirement, and configured classes. The board and cooldown settings can also affect availability.
The payout is lower than expected: check vehicle condition. The class reward is the starting value, and damage adjustments apply at delivery.