> For the complete documentation index, see [llms.txt](https://docs.cuxial.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cuxial.com/scripts/vehicles/cuxial-gasstations.md).

# Cuxial Gas Stations

Player-owned gas stations for FiveM: fuel stock, delivery fleet, staff, pressure washing, detailing and an admin panel.

Cuxial Gas Stations turns every gas station on the map into a business a player can buy and run: stock the tanks, set the pump prices, hire staff and sell services. Pressure washing and detailing are part of the same resource, and staff manage everything from an in-game admin panel.

## What it does

* **Stations for sale.** Each station has its own price, cash box, statistics and map blip. The owner can rename it and pick the blip colour and icon.
* **Fuel stock and prices.** Four fuels plus two electric chargers, each with its own tank and price. A station that stays almost empty for too long is lost.
* **Supply contracts.** The owner or an employee drives a fleet vehicle to import fuel or export the surplus, with a hose-and-bay loading sequence and a mission overlay.
* **Delivery fleet.** Vans, trucks and tankers bought from the station cash box. Capacity decides the litres of each run.
* **Delivery jobs.** The owner posts paid jobs so other players bring the fuel.
* **Staff with three roles**, manual commissions and automatic commissions on services.
* **Upgrades**: tank capacity, garage slots, supplier discount, pressure washers and detailing.
* **Pressure washers.** Paid wash bays at the station (rinse, foam, wax) with a staged wash: soap, sponge, rinse and wax. Public washers with no owner are also supported.
* **Detailing van**: own use, hourly rental to other players and mobile detailing at the customer's location.
* **NPC customers** that drive in to get their car washed while an employee is on shift.
* **Promotions**: happy hours and a free wash when refuelling.
* **Reputation** from 1 to 5 stars, driven by ratings, with effects on NPC traffic and supplier prices.
* **Owner notices**: low stock, waiting customers, lost vans and a daily summary, in game, by phone or to Discord.
* **Fuel spills** next to the pumps that can catch fire and have to be cleaned.
* **Admin panel** with an overview of every station, live rules per station, activity monitors, an audit log and a point editor on the map.

How each of these works in game is covered in the [Features guide](/scripts/vehicles/cuxial-gasstations/features.md).

## Requirements

| Resource                             | Required | Used for                                                                 |
| ------------------------------------ | -------- | ------------------------------------------------------------------------ |
| OneSync                              | Yes      | Server-side vehicles and state                                           |
| `ox_lib`                             | Yes      | Callbacks, commands, keybinds, locales                                   |
| `oxmysql`                            | Yes      | All station data                                                         |
| `cuxial_bridge`                      | Yes      | Connects to your framework (QBox, QBCore or ESX)                         |
| `sleepless_interact`                 | Yes      | Interaction points on stations, washers and vehicles                     |
| `cuxial_gas_assets`                  | Yes      | Props, detailing van, pressure gun and sounds. Delivered with the script |
| Cuxial Fuel (`cuxial_fuel`)          | No       | Sells fuel from the station tanks at the owner's price. See below        |
| Cuxial Garages (`cuxial_garages`)    | No       | Hands out the keys of fleet and detailing vehicles                       |
| A phone supported by `cuxial_bridge` | No       | Owner notices and mobile detailing requests by phone                     |

{% hint style="warning" %}
Fuel sales require a fuel script that reports each sale through the [exports](/scripts/vehicles/cuxial-gasstations/developers.md). Cuxial Fuel does this out of the box. Buying stations and the wash services work without one.
{% endhint %}

## Pages

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Installation</strong></td><td>Dependencies, convars, permissions and start order.</td><td><a href="/scripts/vehicles/cuxial-gasstations/installation.md">Installation</a></td></tr><tr><td><strong>Features guide</strong></td><td>How owners, staff, customers and admins use it in game.</td><td><a href="/scripts/vehicles/cuxial-gasstations/features.md">Features guide</a></td></tr><tr><td><strong>Configuration</strong></td><td><code>shared/config.lua</code> and <code>data/stations.lua</code>, block by block.</td><td><a href="/scripts/vehicles/cuxial-gasstations/configuration.md">Configuration</a></td></tr><tr><td><strong>Commands &#x26; permissions</strong></td><td>Commands, keys, admin access and staff roles.</td><td><a href="/scripts/vehicles/cuxial-gasstations/commands.md">Commands &amp; permissions</a></td></tr><tr><td><strong>Exports &#x26; events</strong></td><td>Connect a fuel script, read prices and reputation, request a wash.</td><td><a href="/scripts/vehicles/cuxial-gasstations/developers.md">Exports &amp; events</a></td></tr><tr><td><strong>Troubleshooting</strong></td><td>Common problems and how to fix them.</td><td><a href="/scripts/vehicles/cuxial-gasstations/troubleshooting.md">Troubleshooting</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cuxial.com/scripts/vehicles/cuxial-gasstations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.