> For the complete documentation index, see [llms.txt](https://documentation.rcore.cz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.rcore.cz/paid-resources/rcore_clothing/configs/config_price.md).

# Price config

You can change pricing of clothes in bulk by changing the `configs/config_price.lua` file.

## Global price multiplier

* `Config.GlobalPriceMultiplier`
  * Multiplies all prices by this value
  * Default: `1.0`

## Multiplier per shop type

If you want to make only certain shop more expensive, you can set a multiplier for each shop type.

```lua
Config.ShopMultiplier = {
    binco = 1.0,
    suburban = 5.0,
    ponsonbys = 15.0,
    ammunation = 4.0,
    beach_masks = 4.0,
    vangelico = 30.0,
    -- some_custom_shop = 1.0,

    -- used when shop is not found
    -- or for items shared across all shops
    -- like undershirts, neckwear, earrings, ...
    default = 1.0,
}
```

## Make everything free in every shop

If you want to make everything free in every shop, you can set `Config.EverythingEverywhereIsFree` to `true`.

If you want only some shops to be free, check the [Shop configs page](/paid-resources/rcore_clothing/configs/shop_configs.md).

## Make character features paid

If you want to make character features like hair, face, etc. paid, you can configure it in `Config.CharFeaturesPrices`

By default, everything costs 0, thus making it free.

These prices still respect EverythingEverywhereIsFree and shop modifiers, so when everything in shop/all shops is supposed to be free, these prices will be ignored.

```lua
Config.CharFeaturesPrices = {
    [SHOP_STRUCTURE.CHAR_PED_SELECT] = 0,
    [SHOP_STRUCTURE.CHAR_HEADBLEND] = 0,
    [SHOP_STRUCTURE.CHAR_NONFREEMODE_HEAD] = 0,
    [SHOP_STRUCTURE.CHAR_FACE_FEATURES] = 0,
    [SHOP_STRUCTURE.CHAR_BLEMISH] = 0,
    [SHOP_STRUCTURE.CHAR_AGE] = 0,
    [SHOP_STRUCTURE.CHAR_COMPLEXION] = 0,
    [SHOP_STRUCTURE.CHAR_SUN_TAN] = 0,
    [SHOP_STRUCTURE.CHAR_MOLES] = 0,
    [SHOP_STRUCTURE.CHAR_BODY_BLEMISH] = 0,
    [SHOP_STRUCTURE.CHAR_EYE_COLOR] = 0,
    [SHOP_STRUCTURE.HAIR_HAIR] = 0,
    [SHOP_STRUCTURE.HAIR_BEARD] = 0,
    [SHOP_STRUCTURE.HAIR_EYEBROWS] = 0,
    [SHOP_STRUCTURE.HAIR_CHEST] = 0,
    [SHOP_STRUCTURE.MAKEUP_MAKEUP] = 0,
    [SHOP_STRUCTURE.MAKEUP_BLUSH] = 0,
    [SHOP_STRUCTURE.MAKEUP_LIPSTICK] = 0,
}
```

To make for example makeup cost 1000 dollars (or your server currency), you would change it like this:

```lua
[SHOP_STRUCTURE.MAKEUP_MAKEUP] = 1000,
```


---

# 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://documentation.rcore.cz/paid-resources/rcore_clothing/configs/config_price.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.