> 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/overview.md).

# Overview

Throw, place and hand over ox\_inventory items, each with its own synced world prop. No ox\_inventory edits required.

Instead of every dropped item turning into the same generic bag, each item gets its own prop – water shows a bottle, a pistol shows the pistol. Players hold the item in their hand, then throw it with physics, place it precisely with a preview, or hand it straight to another player. Everything is synced for all players and validated server-side.

The script hooks into ox\_inventory's official `swapItems` hook, so **no ox\_inventory files need to be edited**.

## Where to go next

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-list-check" style="color:$primary;">:list-check:</i></h3></td><td><strong>Requirements</strong></td><td>Dependencies and supported frameworks.</td><td><a href="/rayn-scripts-docs/rayn_itemdrops/requirements.md">Requirements</a></td></tr><tr><td><h3><i class="fa-rocket" style="color:$primary;">:rocket:</i></h3></td><td><strong>Installation</strong></td><td>Get rayn_itemdrops running on your server.</td><td><a href="/rayn-scripts-docs/rayn_itemdrops/installation.md">Installation</a></td></tr><tr><td><h3><i class="fa-hand-pointer" style="color:$primary;">:hand-pointer:</i></h3></td><td><strong>Usage</strong></td><td>Controls for holding, throwing and placing.</td><td><a href="/rayn-scripts-docs/rayn_itemdrops/usage.md">Usage</a></td></tr><tr><td><h3><i class="fa-sliders" style="color:$primary;">:sliders:</i></h3></td><td><strong>Configuration</strong></td><td>Every option in config.lua and the prop list.</td><td><a href="/rayn-scripts-docs/rayn_itemdrops/configuration.md">Configuration</a></td></tr><tr><td><h3><i class="fa-terminal" style="color:$primary;">:terminal:</i></h3></td><td><strong>Commands</strong></td><td>Admin cleanup command.</td><td><a href="/rayn-scripts-docs/rayn_itemdrops/commands.md">Commands</a></td></tr><tr><td><h3><i class="fa-circle-question" style="color:$primary;">:circle-question:</i></h3></td><td><strong>Troubleshooting</strong></td><td>Fixes for the most common issues.</td><td><a href="/rayn-scripts-docs/rayn_itemdrops/troubleshooting.md">Troubleshooting</a></td></tr></tbody></table>


---

# 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/overview.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.
