# DXS Creator

<figure><img src="/files/msA3ATyvwxBJNr2Qp6uK" alt=""><figcaption></figcaption></figure>

### Dependencies

* FXServer (cerulean)
* `es_extended` or `qb-core` (select via config)
* `oxmysql`
* Optional phone resources for bank notifications: `qs-smartphone`, `qb-phone`, `gksphone`, `gcphone`

### Installation

1. Place the resource in `resources/[dxs]/DXS_creator`.
2. Ensure dependencies are started before this resource.
3. Import `sql/dxs_creator.sql` (optional; tables are also created automatically at runtime).
4. Add to `server.cfg`:

   ```
   ensure DXS_creator
   ```
5. Restart the server.

### Configuration

Edit `config.lua`:

* `Framework`: `esx` or `qbcore`
* `AdminGroup`: ESX group or QBCore permission allowed to use `/creator`
* `EnableNewRobberySystem`: must be `true` to open the creator menu
* `Debug`: enable debug output
* `BlackMoneyType`: QBCore money type used for `black_money` (default: `cash`)

### Commands

* `/creator` - open the creator UI (admin group only)
* `/dv` - delete the closest vehicle
* `/dvadmin` - delete the closest vehicle (admin)
* `/doorinfo` - debug a door entity for the door lock creator

### Data Files

* `html/blips.json` and `html/blipColors.json` for blip UI data.
* `html/vehicle_catalog.json` for dealership catalog and previews.

### Database

* Schema in `sql/dxs_creator.sql`.
* Tables also created automatically on resource start if missing.

### Notes

* `/creator` only opens when `Config.EnableNewRobberySystem = true`.
* When `Framework = qbcore`, vehicles are stored in `player_vehicles` (mods JSON in `mods`).
* Dealership purchases store the selected color in vehicle props for correct paint on spawn.


---

# Agent Instructions: 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:

```
GET https://dxs-scripts.gitbook.io/home/documentation/fivem/dxs-creator.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.