# Setting up the shop

{% hint style="warning" %}
Only start configuring the shop if you have followed the installation guide and the script works without any issues!&#x20;
{% endhint %}

{% hint style="info" %}
You have to have the right rank to be able to open this setting panel inside of the premium shop panel. You can set it in the config.lua

<img src="/files/mUjFcMLmkBjsVa3hFWHk" alt="" data-size="original">
{% endhint %}

<div align="center" data-with-frame="true"><figure><img src="/files/RDsi86pYMey0GbNcnYlJ" alt="" width="83"><figcaption></figcaption></figure></div>

## Create a category

<div align="center" data-full-width="false" data-with-frame="true"><figure><img src="/files/UhspHFuMHL6Gm2BD9tUi" alt="" width="375"><figcaption></figcaption></figure></div>

{% stepper %}
{% step %}

### Select a type for the category&#x20;

<div data-with-frame="true"><figure><img src="/files/7COXkNQHOtkj4jGvdeAt" alt=""><figcaption></figcaption></figure></div>

<mark style="color:$info;">There are 5 different types you can choose from.</mark>&#x20;

<details>

<summary>Vehicle</summary>

<mark style="color:$info;">This type is for the vehicles. In this category there is a button for test driving the vehicle for the customers. And this type has filter search.</mark>&#x20;

<div data-with-frame="true"><figure><img src="/files/itMn8nW8VOGlvLR6GTHK" alt="" width="156"><figcaption></figcaption></figure></div>

</details>

<details>

<summary>Property (with/without filter)</summary>

<mark style="color:$info;">This type is for the properties. In this category there is a button for pinning the location of the proprty for the customers. And this type has a filter search variant and one without the filters.</mark>&#x20;

<div data-with-frame="true"><figure><img src="/files/cfGPnsrGrbRpU64XAu0r" alt="" width="154"><figcaption></figcaption></figure></div>

</details>

<details>

<summary>Basic (with/without filter)</summary>

<mark style="color:$info;">This type is for everything else. In the category there isn't any special buttons for the customers. And this type has a filter search variant and one without the filters.</mark>&#x20;

<div data-with-frame="true"><figure><img src="/files/FC8Iedj9gYV9l3AoOLgN" alt="" width="153"><figcaption></figcaption></figure></div>

</details>
{% endstep %}

{% step %}

### Fill out the name of the category&#x20;

<mark style="color:$info;">All characters lowercase and without space and any special character. This won't be visible to players.</mark>
{% endstep %}

{% step %}

### Fill out the label of the category&#x20;

<mark style="color:$info;">Write here anything you want. This will be visible for players.</mark>&#x20;
{% endstep %}
{% endstepper %}

## Create an item&#x20;

<div data-with-frame="true"><figure><img src="/files/MCYVEesRoTVlKAkB501R" alt="" width="375"><figcaption></figcaption></figure></div>

{% stepper %}
{% step %}

### Choose the category

<div data-with-frame="true"><figure><img src="/files/OhOTht3SJUPZtnxw8ZjU" alt="" width="414"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

### Fill out the name of the item

<mark style="color:$info;">Write here anything you want. This will be visible for players.</mark>&#x20;
{% endstep %}

{% step %}

### Set the price of the item

{% endstep %}

{% step %}

### Fill out the filter type part

<mark style="color:$info;">If the category which contains the item has filter search you have to fill this out. Players will be able to use these to search faster.</mark>&#x20;

<div data-with-frame="true"><figure><img src="/files/fUflRsKfBYe5zJmIcs9e" alt="" width="230"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Fill out the player get part

{% hint style="success" %}
This is where you can set what the player will rechieve when they purchase this item. You can give **anything** to the player. In the sv-utils.lua file you can edit the *GrantPurchase* function if you want to give something which is not pre-configured.
{% endhint %}

#### Here are the things you can set here with the basic sv-utils.lua file

<details>

<summary>Item</summary>

```json
{"type":"item", "name":"water", "amount":1}
```

</details>

<details>

<summary>Vehicle</summary>

```json
{"type":"vehicle", "model":"rapidgt"}
```

</details>

<details>

<summary>Money</summary>

```json
{"type":"money", "amount":1}
```

</details>

<details>

<summary>Property</summary>

```json
{"type":"property", "propertyID":"H101"}
```

Supported property scripts: brutal\_housing, origen\_housing, rx\_housing, tk\_housing

You can add more in the sv-utils.lua *GrantPurchase* function

</details>

<details>

<summary>Gang</summary>

```json
{"type":"gang_business", "gang":"gang_name", "grade":0}
```

{% hint style="danger" %}
The grade is always zero
{% endhint %}

Supported property scripts: brutal\_gangs

You can add more in the sv-utils.lua *GrantPurchase* function

</details>

<details>

<summary>Gang Reputation</summary>

```json
{"type":"gang_reputation", "amount":1}
```

Supported property scripts: brutal\_gangs

You can add more in the sv-utils.lua *GrantPurchase* function

</details>

<details>

<summary>Shop Business</summary>

```json
{"type":"shop_business", "businessID":"BS341"}
```

Supported property scripts: lc\_stores, rx\_playerstores

You can add more in the sv-utils.lua *GrantPurchase* function

</details>

<details>

<summary>Gas Station Business</summary>

```json
{"type":"gas_station_business", "businessID":"BS341"}
```

Supported property scripts: lc\_gas\_stations

You can add more in the sv-utils.lua *GrantPurchase* function

</details>

<mark style="color:$info;">More coming soon...</mark>
{% endstep %}
{% endstepper %}


---

# 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://docs.brutalscripts.com/site/scripts/premium-shop/setting-up-the-shop.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.
