Installation

About ten minutes. There is no SQL to import — the tables and all the default content build themselves on the first start. Each step ends with how you know it worked.

Before you start

You need	Why
oxmysql, started, with a working connection string	Everything lives in the database, including the admin panel’s content
fmLib	Declared as a dependency; the resource will not start without it
glitch-minigames	The hacking minigames during the lockpick step
ESX, QBCore or QBox (optional)	Detected on its own. Without any of them, it runs standalone
ox_target or qb-target (optional)	Only for the matching `Config.InteractionSystem`

1. Put the folder in place

Drop mic_boosting into your resources, for example inside resources/[mic]/.

Keep the folder name mic_boosting. The item name mic_boosting_tablet, the mic_boosting_* tables and everything support will ask you about use that name.

2. Start it after the things it leans on

In server.cfg, ensure mic_boosting goes below oxmysql, your framework (es_extended, qb-core or qbx_core), fmLib, your inventory, your target resource and glitch-minigames.

The one that matters most is oxmysql. The resource waits for it before building its tables; if oxmysql is not started yet, the setup is skipped and the admin panel opens with every tab empty.

It worked when the console shows [MIC-BOOSTING] Server Bridge initialized. Detected Framework: esx (or qbcore — which is also what QBox shows — or standalone) and no red lines from mic_boosting.

3. The database — nothing to do

On the first start the resource creates its mic_boosting_* tables in whatever database oxmysql points at, then fills them with the defaults: six classes, the car pool for each, 28 pickup spots with four guards each, 11 drop-offs, six guard setups, the minigames, the tool shop, challenges, milestones, achievements and perks.

mic_boosting.sql ships at the root of the resource for anyone who prefers to create the schema by hand. You do not need it.

It worked when the console prints a run of [mic_boosting seeder] lines on the first start, and not on later ones.

4. Add the items

Only one item is required: mic_boosting_tablet, the thing players use to open the tablet. The six tool items are sold in the tablet’s Tools tab and only need registering if you want them to work.

Item	What it does
`mic_boosting_tablet`	Opens the tablet. Required in `item` mode
`mic_gps_tracker`	Exact location of the next contract car
`mic_signal_booster`	Smaller search circle for the next contract
`mic_police_scanner`	Delays the police alert on the next contract
`mic_radar_jammer`	A longer police-alert delay
`mic_emp_jammer`	Skips the lockpick minigame once
`mic_fake_plates`	Resets your heat to 0 the moment you buy it

Ready-made definitions ship in the items/ folder — pick the file for your inventory and copy its entries across:

File	For
`items/ox_inventory.lua`	ox_inventory — goes in `ox_inventory/data/items.lua`
`items/qbcore_items.lua`	QBCore — goes in `qb-core/shared/items.lua`
`items/esx_items.lua`	ESX’s own inventory — the rows for your `items` table

The seven images are in items/images/. Copy them to your inventory’s image folder (ox_inventory/web/images/ or qb-inventory/html/images/).

5. Framework and bridge

Config.Framework in config.lua ships as 'auto': it looks for qb-core, then es_extended, and otherwise runs standalone. Force it with 'qbcore', 'esx' or 'standalone' only if detection picks the wrong one.

On QBox, leave it on 'auto': QBox is found through its QBCore compatibility — qbx_core provides qb-core — so there is nothing to set. If you force it, use 'qbcore'.

If your target resource is not ox_target, set Config.InteractionSystem to 'qb_target' or 'drawtext' (a plain E prompt, no target resource needed).

6. Give yourself admin

The admin panel is /boostingconfig. You are an admin if either is true:

you have the ACE named in Config.AdminAce (command by default — txAdmin admins usually have it through group.admin);
your group is listed in Config.AdminGroups (admin, superadmin, god) — the ESX group, or a QBCore permission.

On a standalone server the ACE is the only way in: give group.admin the command ace and add yourself to group.admin in server.cfg.

It worked when /boostingconfig opens the panel on the Locations tab with 28 spots listed.

7. First contract

Give yourself mic_boosting_tablet and a lockpick, and use the tablet.
In the admin panel’s Classes tab, set Min Police Online for class D to 0 for this test. Every class ships needing 2 police online, so on an empty test server you get Not enough police online (0/2) instead of a contract.
On the tablet’s Home tab, join the queue for class D and accept the contract that arrives.

It worked when the car is marked on your map, the lockpick prompt appears on it, the minigame runs, and delivering it at the drop-off adds MB and XP to your profile.

Before you open your city

Put Min Police Online back on every class you changed while testing.
Check Config.PoliceJobs lists your police job names, so the minimum-police count sees them.
Leave Config.ForceDropoffId and Config.ForceLocationId on nil. They pin every contract to one spot and exist only for testing.
Plug in your dispatch. The default police alert is a notification and a blip; to use cd_dispatch, ps-dispatch or another, edit Bridge.PoliceDispatch in bridge/client_bridge.lua.
Make sure lockpick and advancedlockpick can be obtained somewhere in your city.