> For the complete documentation index, see [llms.txt](https://cactus-code.gitbook.io/cactus-code-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cactus-code.gitbook.io/cactus-code-docs/documentation/scripts/cactus-poster-creator/database-and-troubleshooting.md).

# Database and troubleshooting

## Database and troubleshooting

### Database

Default table:

```lua
Config.Database.Table = 'cactus_wanted_posters'
```

| Column                                     | Description              |
| ------------------------------------------ | ------------------------ |
| `id`                                       | Unique identifier.       |
| `board_id`                                 | Board key.               |
| `poster_type`                              | Poster type.             |
| `native_family`                            | `normal` or `legendary`. |
| `native_type`                              | Template from 1 to 5.    |
| `native_difficulty`                        | Difficulty from 1 to 5.  |
| `native_txd`, `native_tex`                 | Texture pair.            |
| `native_slot`                              | Stable slot from 1 to 3. |
| `jurisdiction`, `title`, `subject`, `body` | Main content.            |
| `reward`, `footer`                         | Reward and footer.       |
| `pos_x`, `pos_y`, `pos_z`                  | Position.                |
| `rot_x`, `rot_y`, `rot_z`                  | Rotation.                |
| `creator_identifier`, `creator_name`       | Creator.                 |
| `status`                                   | `active` or `removed`.   |
| `created_at`, `updated_at`                 | SQL timestamps.          |

Removal is non-destructive. The row remains archived with `status = 'removed'`.

### Troubleshooting

#### Empty board at startup

1. Verify the `ensure` order.
2. Verify the `sql/install.sql` import.
3. Enable `Config.Debug = true`.
4. Check TXD preload, bootstrap, native rendering, and write logs.
5. Verify that the TXD/TEX pair exists.

#### Custom texture is invisible

* The `.ytd` file must be in `stream/`.
* TXD must match the dictionary name.
* TEX must match the internal CodeX name.
* Add the pair to `TextureCatalog.Custom`.
* Restart the resource after replacing a YTD file.

#### Cannot add a fourth standard poster

Each family has three slots per board. Use the legendary family or remove a standard poster.

#### Item cannot be found

* Verify `Config.Framework = 'RSG'`.
* Add `RSG_ITEMS.lua` definitions statically if needed.
* Verify item names and images in `rsg-inventory`.

#### Removal is denied

* Verify `job.name`, `job.type`, and the RSG grade.
* Verify `Config.Permissions.Management`.
* Verify `Actions.Remove.Enabled` and `AuthorizedOnly`.
* Verify the `cactus_poster_creator.use` ACE when used.

####

###


---

# 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://cactus-code.gitbook.io/cactus-code-docs/documentation/scripts/cactus-poster-creator/database-and-troubleshooting.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.