# Fishing Script

### 📋 Overview

`NTeamDev Fishing` is a **FiveM script** that allows players to:

* Catch fish
* Clean fish (with XP rewards)
* Sell fish

The script is **framework-agnostic**, meaning it can work with **any major framework or inventory system**, including:

* **Frameworks:** `ESX (es_extended)` and `QB-Core`
* **Inventory systems:** `ox_inventory` (recommended), or any custom inventory
* **Target systems:** Currently `ox_target` (any target system can be implemented)

The script has been **fully tested** and works correctly for fishing, cleaning (with XP), and selling.

### ⚙️ Dependencies

The script currently relies on:

* `ox_lib`
* `ox_target` or `any`          
* `es_extended` or `qb-core`

### 🐟 Fishing Integration with Custom Inventories

If you **don’t use `ox_inventory`**, keep in mind:

* The **fishing item is pre-registered** for `ox_inventory`.
* For other inventory systems, you **must create your own item**.

Then, use the provided event to start fishing:

```lua
TriggerClientEvent('nteamdev_fishing:client:startFishing', source)
```

**Event name:**

```
nteamdev_fishing:client:startFishing
```

This event must be triggered for your custom inventory to integrate properly with the fishing system.

***

### ✅ Features

* 🎣 **Fishing system** with item collection
* ✂️ **Fish cleaning** with optional XP gain
* 💰 **Fish selling** system
* 🌐 **Framework flexible** – works with ESX or QB-Core
* 🔧 **Inventory agnostic** – supports ox\_inventory and custom inventories
* 🎯 **Target system ready**


---

# 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://nteamdev.gitbook.io/nteam-development/fishing-script.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.