# Configuration

The main configuration file is `0r-farming-v2/config.lua`.

## Main Settings You Will Usually Change

| Field                                | What it controls                            |
| ------------------------------------ | ------------------------------------------- |
| `Config.InventoryImagesFolder`       | Folder path used for item images            |
| `Config.FarmingMenu.openWithCommand` | Open menu with command                      |
| `Config.FarmingMenu.openWithKey`     | Open menu with keybind                      |
| `Config.FarmingMenu.openWithItem`    | Open menu with an item                      |
| `Config.FarmingMenu.allowedJobs`     | Restrict menu access to specific jobs       |
| `Config.Levels`                      | Experience requirements for each level      |
| `Config.InfoBoxAlign`                | Task info box alignment                     |
| `Config.ToggleInfoBoxKey`            | Toggle extra task information               |
| `Config.CleanMoney`                  | Clean money handling                        |
| `Config.SellNpc`                     | NPC model, blip, and sell locations         |
| `Config.HelpText`                    | In-menu help entries                        |
| `Config.DisableCustomProps`          | Disable custom props at farming locations   |
| `Config.DisableCustomMarkers`        | Disable custom markers at farming locations |
| `Config.debug`                       | Debug mode                                  |

## Farming Menu Access

`Config.FarmingMenu` supports 3 ways to open the menu:

* Command
* Keybind
* Item

Most servers keep only one or two enabled.

## Example Menu Configuration

```lua
Config.FarmingMenu = {
    openWithCommand = {
        active = true,
        command = "farmingmenu",
    },
    openWithKey = {
        active = true,
        key = "F7",
    },
    openWithItem = {
        active = true,
        itemName = "farming_tablet",
    },
    allowedJobs = {},
}
```

## Levels and Progression

The script uses a level table:

```lua
Config.Levels = { 0, 1000, 2000, 4000, 8000, 10000, 15000 }
```

You can rebalance progression by changing these values.

## Money and Sell NPC

The `Config.CleanMoney` section controls whether rewards are given as an item or account money.

The `Config.SellNpc` section controls:

* NPC model
* Blip settings
* Sell locations

The script also has a separate market config here:

```lua
core/market/config.lua
```

This file controls market buy/sell entries, prices, sell prices, labels, descriptions, and level requirements for each farming item.

## Help Text

The built-in help entries shown in the farming menu are configured inside `Config.HelpText`. You can edit or remove these entries to match your server.

## Personal Challenges and Multiplayer Tasks

The gameplay system is split into clear config areas:

* `core/personal_challenges/config.lua`
* `core/multiplayer_tasks/freelance/config.lua`
* `core/multiplayer_tasks/livestock_farming/config.lua`
* `core/multiplayer_tasks/melon_pumpkin/config.lua`

That means you can rebalance challenge goals, rewards, and task behavior without changing the main menu config.

## Localization

This resource uses locale files in the `locales/` folder. The original docs reference the standard `ox_lib` locale flow:

```cfg
set ox:locale "en"
```

If you want another language, create a matching locale file using the same structure as the default locale.


---

# 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.0resmon.org/0resmon/0r-resources/0r-farming-v2/configuration.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.