> 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/paid-resources/used-vehicle-dealership/commands.md).

# Commands

## Player Command

### `/usedcars`

Opens the Used Vehicle Dealership UI while the player is physically at a configured dealership.

The command name is configurable:

```lua
Config.Command = 'usedcars'
```

Normal dealership access still uses the configured dealership location and interaction system.

## Admin Command

### `/usedvehiclesadmin`

Opens the staff Admin Panel for authorised users.

```lua
Config.AdminCommand = 'usedvehiclesadmin'
Config.AdminAce = 'otters_usedvehicles.admin'
```

Unlike the normal player command, `/usedvehiclesadmin` can be used **from anywhere on the map** by a player with the configured ACE permission.

The Admin Panel allows authorised staff to manage active listings and sellers, including editing/removing listings and banning/unbanning sellers.

## ACE Permission

Example:

```cfg
add_ace identifier.license:YOUR_LICENSE otters_usedvehicles.admin allow
```

You can grant the permission to a group instead:

```cfg
add_ace group.admin otters_usedvehicles.admin allow
```

The configured ACE is validated server-side.

## Staff Price Bypass

The listing anti-abuse price limits have a separate optional staff bypass ACE:

```lua
StaffBypassAce = 'otters_usedvehicles.staff'
```

Example:

```cfg
add_ace group.admin otters_usedvehicles.staff allow
```

## Showcase Test Command

When `Config.AdminTestMode.Enabled = true`, authorised staff can use:

```
/usedvehiclestest
/usedvehiclestest VEHICLEMODEL
/usedvehiclestest off
```

The command spawns local test vehicles into the configured showcase slots so staff can check positioning without creating real listings. `DefaultVehicle` controls the model used when no model is supplied, and `ShowSlotLabels` controls the slot/coordinate labels.


---

# 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://otters-developments.gitbook.io/otters-developments/paid-resources/used-vehicle-dealership/commands.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.