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

# FAQ

## Which resource should I install first?

Install `reddev_devtablet` first. Then add optional resources such as Music, Drug Creator, Garage Creator, Door Creator, and House Creator.

## Which resources need SQL?

SQL setup was found for `reddev_devtablet`, `doors_creator`, `drug_creator`, `garage_creator`, `reddev_housecreator`, and optional `reddev_music` tables.

## Which resources need inventory items?

Item setup was found for `reddev_devtablet`, `reddev_music`, `drug_creator`, `ammo_boxes`, `reddev-bodybag`, and `reddev_housecreator`.

## Which resources are tablet apps?

Tablet integration was found for `reddev_devtablet`, `doors_creator`, `drug_creator`, `garage_creator`, `reddev_housecreator`, and `reddev_music`.

## Can optional tablet apps be missing?

Yes. The tablet plugin docs state optional app icons hide when the app resource is stopped or missing.

## Do I need screenshots before publishing?

Fresh screenshots are recommended for the public GitBook/Tebex experience. The existing tablet screenshot guide recommends captures for Home Screen, Admin Menu, Creator Apps, Optional Apps, Runtime Menus, Drug Creator, Garage Creator, Weather and Time, and REDDEV Music.

## What should I not rename?

Do not rename streamed House Creator props files, model identifiers, or resource folders that tablet app registration depends on. Keep app IDs like `garage_creator`, `drug_creator`, and `door_creator` stable.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://reddev-development.gitbook.io/reddev-development-docs/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.