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

# Configuration & creator

Configuration examples, supported options and setup checks.

## Compatibility

Edit `config.lua`:

```lua
Config.Framework = 'auto' -- auto, esx, qb, qbox, standalone
Config.Inventory = 'auto' -- auto, ox_inventory, qb, none
Config.Target = 'auto'    -- auto, ox_target, qb-target, marker, none
Config.TextUI = 'auto'    -- auto, ox_lib, none
Config.Locale = 'en'
```

## Create and restrict an elevator

1. Grant `add_ace group.admin tn_elevator.creator allow` in `server.cfg`.
2. Run `/elevatorcreator`; create an elevator with a unique name.
3. Add destination floors, record their positions and set separate call buttons.
4. Choose the default floor and allow/block vehicles.
5. Set access rules on the whole elevator or individual floors: job/grade, item, passcode and optional hacking. Configure the required hack item if used.
6. Save and test with an allowed and a restricted character.

Required access/hack items must already exist in the selected inventory. No dedicated elevator item is mandatory.

## Timing and interactions

| Setting                        | Default / unit |
| ------------------------------ | -------------- |
| `Config.InteractDistance`      | 1.7 m          |
| `Config.TextUIDistance`        | 0.85 m         |
| `Config.DrawDistance`          | 14.0 m         |
| `Config.TravelSecondsPerFloor` | 2.4 seconds    |
| `Config.MinTravelSeconds`      | 4.0 seconds    |
| `Config.ArrivalCloseDelay`     | 2600 ms        |
| `Config.RiderRadius`           | 2.6 m          |
| `Config.RiderDecisionTimeout`  | 10000 ms       |

Nearby players receive a ride invitation; pending riders are accepted after the configured decision timeout.

## Persistence and integration

Keep `Config.Elevators = {}` for creator-managed setups. Definitions persist in `data/elevators.json`; preserve it during updates. Players move to saved floor coordinates after the travel sequence.

This version declares no public Lua exports. Use the creator and configured interaction points; travel, hacking and synchronization network events are internal lifecycle messages.


---

# 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://tn-modifications.gitbook.io/tn-modifications/tn_elevator/configuration.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.
