> For the complete documentation index, see [llms.txt](https://docs.av-scripts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.av-scripts.com/laptop-pack-v3/racing/installation/vehicle-classes.md).

# Vehicle Classes

**How are classes calculated?**&#x20;

We use a custom algorithm that reads the vehicle's handling data. The formula combines Speed, Handling, and Braking, but places the highest priority on Acceleration.

* **Motorcycles:** Are always placed in Class M, regardless of stats.
* **Cars:** Are placed in S+, S, A+, A, B, C, or D based on a calculated score.&#x20;
* If you modify a car's handling file (e.g., increase the drive force), the script will automatically detect the change and may promote the car to a higher class.

If you want to modify this function you can find it in `av_laptop/client/editable/vehicle_classes.lua`


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.av-scripts.com/laptop-pack-v3/racing/installation/vehicle-classes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
