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

# Overview

**Advanced stance and wheel fitment system for FiveM**

> **Requires** [**zloma\_core**](https://github.com/ZlomaScripts/zloma_core) so the same resource works across ESX, QBCore, and QBox without separate versions.

zloma\_stance is a fitment resource focused on persistent wheel offset and camber tuning. It gives you configurable stance stations, live preview before saving, server-backed plate-based persistence, and cross-client visual sync so spawned vehicles keep their wheel setup consistently across the session.

***

## Highlights

| Feature                    | Description                                                                   |
| -------------------------- | ----------------------------------------------------------------------------- |
| **Live Tuning UI**         | Open the menu in a configured station and preview stance/camber before saving |
| **Per-Plate Persistence**  | Saved data is stored in the framework vehicle table under the `wheels` column |
| **Auto Database Setup**    | On first start, the script creates the `wheels` column if it does not exist   |
| **Spawn Reapply**          | Saved fitment can be reapplied automatically when a vehicle is spawned        |
| **Cross-Client Sync**      | Active fitment is replicated with state bags and session cache                |
| **Flexible Access Modes**  | Each station can be public, job-locked, identifier-locked, or mixed           |
| **Multiple Entry Methods** | Use command, TextUI prompt, target box zone, or a physical target prop        |
| **Framework Agnostic**     | Vehicle table selection is auto-detected for ESX, QBCore, and QBox            |

***

## How It Works

1. A player enters a configured fitment zone.
2. The script checks whether that player can use the zone.
3. The stance UI loads the vehicle's saved wheel data by plate if it exists.
4. The player previews offset and camber changes locally.
5. On apply, the data is saved to the database and the active session cache is updated.
6. When the vehicle spawns later, the saved data can be pushed back onto the entity automatically.
7. Players who join later receive the active fitment pool so already-spawned vehicles still look correct.

***

## Dependencies

| Resource     | Required | Purpose                                                         |
| ------------ | -------- | --------------------------------------------------------------- |
| `ox_lib`     | Yes      | Callback system, progress bar, and UI helpers                   |
| `oxmysql`    | Yes      | Database access and schema management                           |
| `zloma_core` | Yes      | Framework abstraction, notifications, and target wrapper        |
| `ox_target`  | Optional | Required only if `Config.UseMethod` is `Target` or `TargetProp` |

***

## Escrow Layout

Open files for an escrow build:

* `config.lua`
* `shared/*.lua`

That keeps server owners able to change configuration and shared bridge/locale logic without opening the protected fitment implementation.

***

## Quick Links

* [Installation](/zloma-scripts/zloma_stance-free-escrow/installation.md)
* [Configuration](/zloma-scripts/zloma_stance-free-escrow/configuration.md)
* [API Reference](/zloma-scripts/zloma_stance-free-escrow/api-reference.md)

***

## Availability

zloma\_stance is a free resource.

**Discord:** [discord.gg/ccAz3NJGCt](https://discord.gg/ccAz3NJGCt)


---

# 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:

```
GET https://zloma-scripts.gitbook.io/zloma-scripts/zloma_stance-free-escrow/zloma_stance.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.