> For the complete documentation index, see [llms.txt](https://docs.polat.shop/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.polat.shop/scripts/farmer-jobs-v2/payment-and-boss.md).

# Payment and Boss

## 💵 <mark style="color:orange;">Payment System</mark>

<mark style="color:blue;">Players receive payment for each row they complete. The total amount is calculated by multiplying the number of parcels in the row by the payment value per parcel.</mark>

<mark style="color:blue;">**Example:**</mark>\ <mark style="color:blue;">If a row contains 30 parcels and the planting job pays 52 per parcel, the player earns</mark>\ <mark style="color:blue;">**30 × 52 = 1560**</mark><mark style="color:blue;">.</mark>

<mark style="color:blue;">Payment rates can be adjusted via the</mark> <mark style="color:blue;"></mark><mark style="color:blue;">`PLT.Payments`</mark> <mark style="color:blue;"></mark><mark style="color:blue;">table inside</mark> <mark style="color:blue;"></mark><mark style="color:blue;">`config.lua`</mark><mark style="color:blue;">.</mark>\ <mark style="color:blue;">Each job type (planting, harvesting, baling, etc.) has its own configurable payment value.</mark>

<mark style="color:blue;">Additionally,</mark> <mark style="color:blue;"></mark><mark style="color:blue;">`config.lua`</mark> <mark style="color:blue;"></mark><mark style="color:blue;">defines how many parcels a player can complete per hour for each job stage.</mark>\ <mark style="color:blue;">When the script is restarted, the server console prints estimated hourly income and rental costs based on those values.</mark>

***

## 🏢 <mark style="color:orange;">Company System</mark>

<mark style="color:blue;">The script is integrated with a company account system.</mark>\ <mark style="color:blue;">The company balance is automatically updated based on all player payments and rental transactions.</mark>

* <mark style="color:blue;">Salaries paid to players are deducted from the company account.</mark>
* <mark style="color:blue;">Rental fees paid by players are added directly to the company account.</mark>
* <mark style="color:blue;">Deposits paid by players are also transferred to the company. If the vehicle is not returned, the deposit remains with the company.</mark>

<mark style="color:blue;">Additionally:</mark>

* <mark style="color:blue;">Grains harvested and bales collected by players are stored in the company warehouse.</mark>
* <mark style="color:blue;">The company owner can sell these grains and bales to generate income.</mark>
* <mark style="color:blue;">The sale prices for grains and bales can be configured via the</mark> <mark style="color:blue;"></mark><mark style="color:blue;">`config.lua`</mark> <mark style="color:blue;"></mark><mark style="color:blue;">file.</mark>

<mark style="color:blue;">When the script is restarted, product sale costs (based on player wages) are calculated and printed to the server console.</mark>\ <mark style="color:blue;">This cost estimation assumes players work at optimal speed. However, if they idle or fail to return vehicles, they may pay extra rental fees or lose their deposit — which results in extra profit for the company.</mark>

<mark style="color:blue;">There is also a dedicated</mark> <mark style="color:blue;"></mark><mark style="color:blue;">**Discord Webhook**</mark> <mark style="color:blue;"></mark><mark style="color:blue;">system for company management.</mark>\ <mark style="color:blue;">All salary payments, rental income, deposit transactions, sales, and cash withdrawals are logged in detail via Discord Webhook for server admins.</mark>

***

## 🖥 <mark style="color:orange;">Information Printed to Server Console</mark>

<mark style="color:blue;">When the script starts, based on your config settings, the following information is printed for each job (Planting, Harvesting, Baling, Bale Loading, Bale Storage):</mark>

#### **💰&#x20;**<mark style="color:purple;">**Player Earnings**</mark>

<mark style="color:blue;">For each job: estimated hourly gross income, rental costs, and net profit are calculated.</mark>

#### <mark style="color:blue;">**💰**</mark>**&#x20;**<mark style="color:purple;">**Product Costs & Sale Profits**</mark>

<mark style="color:blue;">The unit production cost of each product (e.g., wheat or hay bale) is calculated.</mark>\ <mark style="color:blue;">Sale prices are retrieved from the config file, allowing the system to adapt automatically if prices change.</mark>\ <mark style="color:blue;">By comparing production costs and sale prices, the company’s profit per unit is determined.</mark>\ <mark style="color:blue;">This helps admins clearly understand how much profit the company earns indirectly through player activity.</mark>

#### **📦** <mark style="color:purple;">**Additional Info**</mark>

<mark style="color:blue;">Other details such as total company balance, silo stock levels, and logs of past salaries and rental income are also printed to the console.</mark>\ <mark style="color:blue;">Defined managers (Boss IDs) are listed in the logs.</mark>


---

# 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://docs.polat.shop/scripts/farmer-jobs-v2/payment-and-boss.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.