# Item Drop Feed

Drop Feed is a modern FiveM item drop & loot system that turns dropped items into clean 3D world props with glow effects and an inspect card next to the item. Fully configurable , optimized for performance, it gives your QBCore/ESX/QBOX server a polished, readable, and stylish drop feed instead of default text spam.

### Purchase the Script

{% embed url="<https://ambr4scripts.com/products/dropfeed>" %}

### Showcase

{% embed url="<https://www.youtube.com/watch?v=ShzSDT2EeDo>" %}

### Features

#### 🔧 Fully configurable via config.lua

* Control distances, lifetimes, merge window, NUI behavior, models, glow, inspect data and more.

#### 🧾 Modern stacked drop feed UI

* Clean vertical feed showing each event with item icon, label and amount – like a killfeed, but for drops and loot. Easy for players to see what was dropped or picked up at a glance.

#### 🔁 Smart merging of repeated events

* Repeated drops of the same item within the configured MergeWindow are merged into a single line with updated quantity, keeping the feed readable and non-spammy.

#### 📦 3D world props for dropped items

* Each item can use its own world model via Config.DropProps, with a default fallback for any undefined items.

#### 🧭 Smart world placement

* Props align to the ground, inherit player heading, and can be frozen in place for a clean, non-jittery look.

#### ♻️ Automatic spawn & despawn

* Props spawn automatically when ox\_inventory delta is negative (dropping items) and despawn around the pickup radius.

#### 🌈 Glow groups and color-coded loot

* Built-in glow system with configurable range, intensity, day multiplier and color groups (yellow/blue/green/red) for different item types (weapons, meds, tools, resources, etc.).

#### ✨ Pulse or steady light modes

* Choose constant or pulsing glow, with adjustable pulse speed for eye-catching drops.

#### 🖼️ Optional outline glow

* Extra outline highlight around drops, with its own RGBA color, intensity range and day multiplier.

#### 🔍 Inspect card next to the item

* Shows a modern inspect panel near the drop with name, tags (e.g. SIDEARM, MID RANGE, UTILITY) and custom descriptions per item.

#### 🏷️ Custom tags & descriptions per item

* Fine-tune the feeling of each item type: weapons, water, radio, lockpick, phone and more with Tags and Descriptions.

#### 🧩 Shared icons for attachments

* Use a single image for multiple attachment items via AttachmentImageMap (e.g. all suppressor variants share one icon).

#### 📝 Custom labels support

* Override item labels with Config.CustomLabels to match your server’s naming and branding.

#### 🖥️ Clean NUI drop feed behavior

* Control how long entries stay visible (LifeTime) and how fast repeated events get merged (MergeWindow) for a non-spammy HUD.

#### ⚙️ ox\_inventory watchdog integration

* Config.OxWatchdog and interval handling ensure stable syncing with ox\_inventory item changes.

#### 🪶 Lightweight and performance-friendly

* Designed to be visually rich but minimal on MS usage, suitable for high-pop servers.

***

{% hint style="success" %}
Drop Feed works out of the box with **ox\_inventory**, **codem-inventory**, **qb-inventory**, and the **default ESX inventory**. It supports **ESX**, **QBCore**, **QBOX** and **Ox**-based frameworks.\
It also supports **custom inventory systems** that reuse or forward the same triggers/events from these inventories (drop / remove / add item events).\
If you need support for a different inventory system, please contact our support and we will add the integration for you.
{% endhint %}


---

# 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://ambr4-scripts.gitbook.io/docs/scripts/item-drop-feed.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.
