# Envi-Sabotage

***

## Prerequisites

{% hint style="info" %}

* A working FiveM server
* Basic resource setup knowledge
* Followed [FIRST STEPS (READ FIRST)](/documentation/premium-scripts/first-steps-read-first.md)
* `envi-bridge`
* `ox_lib`
* A compatible inventory and target integration through the bridge
* InteractSound if you want tool audio
* Optional `envi-addictions` if you enable addiction hooks
  {% endhint %}

***

## [Tebex](https://envi-scripts.tebex.io/package/5699377)

***

## What this adds

Envi-Sabotage adds item-based vehicle sabotage with synced vehicle state.

Core systems:

* tool props and animations
* wheel, brake, fuel, accelerator, door, and electrics sabotage
* ignition, impact, remote, and speed bombs
* vehicle fires
* mechanic repair flows
* configurable skill checks
* server-authoritative sync for late joiners
* optional addiction point hooks

### Sabotage items

* **Impact Driver** removes wheels.
* **Spanner** loosens wheel nuts.
* **Pliers** cut brake lines.
* **Adjustable Spanner** sabotages acceleration.
* **Drill** creates a fuel leak.
* **Buzz Saw** removes doors.
* **Screwdriver** sabotages electrics.
* **Ignition Bomb** explodes on vehicle start.
* **Impact Bomb** explodes after vehicle impact.
* **Remote Bomb** detonates through the remote item.
* **Speed Bomb** punishes dropping below the armed speed.
* **Firelighter** ignites a nearby vehicle.

### Install

{% stepper %}
{% step %}

### Follow the base load order

Follow [FIRST STEPS (READ FIRST)](/documentation/premium-scripts/first-steps-read-first.md) for the correct load order.

Then verify `ox_lib`, your inventory, and your target stack are already running before you test this resource.
{% endstep %}

{% step %}

### Register the items

Add every enabled tool and bomb item to your inventory.

Item names must match the configured `item` values exactly.
{% endstep %}

{% step %}

### Install optional sound support

If you want drill, saw, and impact-driver audio, install the sound files from `install/sounds/`.

Apply the extra coord playback handlers if your InteractSound build needs them.
{% endstep %}

{% step %}

### Wire optional integrations

If you use fuel leaks, finish the `fuelExport(vehicle)` hook first.

If you use addiction points, enable `envi-addictions` and match the addiction type in config.
{% endstep %}
{% endstepper %}

### Register these items

Default item names:

* `impact_driver`
* `spanner`
* `pliers`
* `adjustable_spanner`
* `drill`
* `buzz_saw`
* `screwdriver`
* `ignition_bomb`
* `impact_bomb`
* `remote_bomb`
* `phone_bomb`
* `speed_bomb`
* `firelighter`

Players need to use the item first.

That equips the prop and unlocks the target options.

### Docs in this section

* [First Time Setup](/documentation/premium-scripts/envi-sabotage/first-time-setup.md)
* [Common Issues](/documentation/premium-scripts/envi-sabotage/common-issues.md)
* [Inventory Setup](/documentation/premium-scripts/envi-sabotage/inventory-setup.md)
* [Systems Overview](/documentation/premium-scripts/envi-sabotage/systems-overview.md)
* [Exports](/documentation/premium-scripts/envi-sabotage/exports.md)

### Good first checks

* If tools do nothing, check the item names first.
* If a bomb will not place, open the hood and target the engine area.
* If tool audio is missing, install the InteractSound assets.
* If late joiners see wrong state, verify the bridge player-loaded hook fires.

***

## Preview

{% embed url="<https://www.youtube.com/watch?embeds_referring_euri=https://envi-scripts.tebex.io/&source_ve_path=OTY3MTQ&v=X1KBDrtzA_g>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://envi-scripts-organization.gitbook.io/documentation/premium-scripts/envi-sabotage.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.