> For the complete documentation index, see [llms.txt](https://rayn-scripts.gitbook.io/rayn-scripts-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rayn-scripts.gitbook.io/rayn-scripts-docs/rayn_itemdrops/how-it-works.md).

# How It Works

Technical overview of the drop flow and security.

## Drop interception

The script registers an ox\_inventory `swapItems` hook. When a player drags an item to the ground, the hook cancels the default bag drop and tells the client to hold the item instead. The item **stays in the inventory** until it is thrown or placed.

## Server-side validation

On every action the server checks that:

* the player still has the item in the same slot (no duplication),
* the distance is valid (throw origin, place position, pickup, hand-over),
* the target player has inventory space,
* cooldowns and the global drop limit are respected.

Item metadata (weapon serials, ammo, durability, custom labels) is preserved.

## Sync

Ground items are stored on the server and sent to players in the same routing bucket. Each client spawns them as **local objects** only within the render distance, so they do not create networked entities. Thrown items are simulated locally for everyone nearby, then replaced with the final position reported by the thrower.

## Persistence

With `Config.Persist = true`, ground items are saved to the resource KVP and restored after a restart. Expired items are removed automatically.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://rayn-scripts.gitbook.io/rayn-scripts-docs/rayn_itemdrops/how-it-works.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.