> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/props/installation.md).

# Installation

How to install a Daddy Studio prop pack and use its models in your scripts.

1. Download the pack from [Cfx Keymaster](/daddy-studios-docs/getting-started/cfx-keymaster-guide.md).
2. Put the folder into your server's `resources`, for example `resources/[props]/`.
3. Add it to `server.cfg`:

   ```
   ensure [props]
   ```
4. Restart the server. The models stream to every player; no script runs.

{% hint style="info" %}
Every pack is its own resource (for Farm Props: `daddy_farmprops_<theme>`). The Complete bundle gives you all of them; ensure the ones you use.
{% endhint %}

## Using the models in a script

Every model's origin is its planting point: Z=0 is the soil line. Create the object on the ground height and it sits right, without `PlaceObjectOnGroundProperly`.

```lua
local model = `daddy_farm_potato_sprout`
RequestModel(model)
while not HasModelLoaded(model) do Wait(0) end
local found, groundZ = GetGroundZFor_3dCoord(x, y, z + 2.0, false)
local plant = CreateObject(model, x, y, groundZ, false, false, false)
FreezeEntityPosition(plant, true)
SetModelAsNoLongerNeeded(model)
```

To let a crop grow, delete the object and create the next stage at the same spot: sprout, growing, mature, then rotten when it is left too long.

## Inventory icons

Each pack has an `inventory/` folder with a 512 px transparent picture of every harvested crop (`<crop>.png`). Copy them where your inventory script reads its item images.

## Notes

* Do not rename the folder or the files inside, the model names come from them.
* Each model has three levels of detail and one draw call, so full fields stay light.
* A small collision box sits around each plant's core: target systems hit it, players still walk between rows.


---

# 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://daddy-studios.gitbook.io/daddy-studios-docs/props/installation.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.