❗Quick Start

Get your first bomb type working in this order.

1

Start the dependencies

Make sure these are running:

• envi-bridge

• ox_lib

• your inventory

• your target system through the bridge

If your bomb uses a custom prop, make sure that prop is streamed too.

2

Register the inventory items

Add every enabled bomb item from Config.Bombs to your item database.

If you use the manual, add Config.ManualItem too.

3

Review one bomb type

Start with a single bomb in shared/config.lua.

Check these fields first:

• item

• prop

• timer

• strikes

• puzzles

• explosion

• fireSettings

• gasSettings

4

Test placement and defusal

Use the bomb item in game.

Then verify:

• timer selection works

• the prop appears

• target options appear in range

• the NUI opens

• success and failure cleanup both work

5

Tune the balance

Adjust these values for your server style:

• timer length

• max strikes

• puzzle count

• Config.TimerSpeedUpChance

• explosion, fire, or gas outcomes

Good first checks

• blank UI usually means the packaged build is missing or outdated

• silent bombs usually mean zone audio expectations are misunderstood

• missing props usually mean the configured model does not exist on the server

• defusal balance usually comes from timer, strikes, and puzzle count together

Start here next

• Bomb Lifecycle and Networking

• Puzzle Modules

• Config Reference