> For the complete documentation index, see [llms.txt](https://otters-developments.gitbook.io/otters-developments/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://otters-developments.gitbook.io/otters-developments/free-resources/rental.md).

# Rental

Otters Rentals is a modern and configurable vehicle rental system for FiveM, supporting **QBCore, Qbox and ESX**.

Create multiple independent rental locations for cars, motorcycles, boats, helicopters and planes from a single resource. Players can interact with a configured rental NPC, browse available vehicles, select a custom colour and rent directly through the custom interface.

## Features

* Modern custom rental UI
* QBCore, Qbox & ESX support
* Car, motorcycle, boat, helicopter & plane rentals
* Multiple independent rental locations
* Configurable NPCs and vehicle spawn points
* Configurable vehicles, prices and categories
* Vehicle search
* RGB/HEX vehicle colour picker
* Configurable rental cooldowns
* Vehicle return system
* Cross-location returns using return groups
* Damage-based refunds
* Vehicle-specific return markers
* Optional licence requirements
* Multiple licence integrations
* Multiple fuel integrations
* Configurable starting fuel
* Multiple target, notification, Text UI and key integrations
* Optional rental papers
* Configurable markers and blips
* Configurable UI theme
* Built-in Press E fallback
* Server-side payment validation
* Automatic framework and integration detection

## Multiple Rental Types

Rental locations operate independently, allowing you to create services such as city car rentals, airport rentals, motorcycle rentals, marina boat rentals, helicopter rentals and plane rentals.

Each location can have its own vehicles, prices, spawn points, cooldown, licence requirement, fuel level, return point and refund settings.

## Vehicle Returns

Players can return rental vehicles to configured return locations. Compatible locations can share a return group, allowing a vehicle rented from one branch to be returned at another.

Refunds can be reduced based on engine and body condition, while the maximum refund percentage remains configurable per location.

## Licence & Fuel Support

Licence checking is optional. Supported approaches documented in the resource include Qbox/QBCore metadata, qbx\_idcard-style systems, ESX licences, inventory items and custom integrations.

Rental vehicles can also receive configurable starting fuel through supported fuel integrations.

## Framework Support

* QBCore
* Qbox
* ESX

## Editable Files

The resource is designed so server-specific configuration and visual customisation can be handled without editing protected runtime logic.

* `config.lua`
* `ui/theme.css`
* `install/` where applicable

## Installation

{% stepper %}
{% step %}

### Place the resource

Place the resource in your server resources folder.
{% endstep %}

{% step %}

### Configure the resource

Configure `config.lua`.
{% endstep %}

{% step %}

### Install optional inventory files

Install any optional inventory files required by your setup.
{% endstep %}

{% step %}

### Add the resource to your start order

Add the resource to your server start order.
{% endstep %}

{% step %}

### Restart and test

Restart the server and test the complete rental and return process.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
For boats and aircraft, make sure spawn and return points have enough clearance for the largest vehicle available at that location.
{% endhint %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://otters-developments.gitbook.io/otters-developments/free-resources/rental.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 `build a script that syncs our docs to a CMS` 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.