Skip to content

Installation

Five minutes, most of it adding the items to your inventory.


You needWhy
ESX, QBCore or QBox, runningThe four usable items are registered through your framework
An inventory that can hold five new itemsox_inventory, qb-inventory or the ESX default all work

Drop mic_carbomb into your resources, for example inside resources/[mic]/. There is no props resource to go with it.


In server.cfg, put ensure mic_carbomb below your framework (es_extended, qb-core or qbx_core) and your inventory.

It worked when the server console shows no red line from mic_carbomb on start. The one you do not want to see is “Invalid framework specified in config.lua. Use ‘esx’ or ‘qbcore’.”


mic_carbomb keeps planted bombs in the server’s memory, not in the database. The only database step is the ESX item rows in step 4, and only if you use the default ESX inventory.


ItemWhat it does
car_bombUse it to hold a bomb, then press E next to a vehicle to plant it
phone_detonatorOpens the detonator phone: your bombs, detonate now or on a timer
bomb_detectorTakes out the scanner; use it again to put it away
bomb_defuserTakes out the toolbox; press E next to a bombed vehicle to defuse
defused_bombNot usable. Given back after a defusal when Config.ReturnDefusedBomb is on

The ready-made definitions ship in inventory_items/, and the icons in inventory_images/:

InventoryDefinitions (mic_carbomb/inventory_items/)Where they goIcons
ox_inventoryox_inventory.mdox_inventory/data/items.luaCopy inventory_images/*.png to ox_inventory/web/images/
QBCore / qb-inventoryqb_inventory.mdqb-core/shared/items.luaCopy them to qb-inventory/html/images/
ESX default inventoryesx_sql_items.mdRun the statement in it once on your database—

It worked when you give yourself one of each and all five show in your inventory with their icon.


Open config.lua and set Config.Framework to esx (the default) or qbcore. There is no auto-detect. On QBox, choose qbcore: QBox runs QBCore resources through its compatibility layer.

While you are there: Config.WebhookEnabled is on out of the box with a placeholder URL. Either paste your Discord webhook into Config.WebhookURL, or set WebhookEnabled to false.


  1. Spawn a vehicle and step out of it.
  2. Use car_bomb. A bomb appears in your hand. Walk up to the vehicle (within 2 m) and press E. The planting animation plays for two seconds and the bomb is gone from your hand.
  3. Use bomb_detector and look at the vehicle. It beeps, and a red blip sits on the vehicle.
  4. Use bomb_detector again to put it away. Walk well clear of the vehicle, but keep it in sight — the detonator can only blow a vehicle that is loaded around you.
  5. Use phone_detonator. The phone lists the vehicle’s model and plate. Press the green key.

It worked when the vehicle explodes and disappears from the phone’s list.

To test defusing, plant a second bomb, use bomb_defuser, stand next to the vehicle and press E. It worked when the repair animation finishes, the beeping stops, and a car_bomb comes back to you.


  • Config.Framework matches the framework you actually run (qbcore on QBox).
  • QBCore: every item name equals its key.
  • The webhook is either a real URL or switched off.
  • config.lua is sent to every player (it is a shared script). Anyone who digs through their client files can read the webhook URL. Use a webhook for a channel you are happy to have spammed, or leave it off.
  • Decide what items cost. Out of the box planting does not use up the bomb (Config.RemoveItem is off), so one car_bomb plants as many bombs as the player likes.