# Using the AutoStancer Feature

### Before you start

{% hint style="info" %}
[**Be sure to download the AutoStancer tool here.**](https://github.com/LegacyDMC/TrueStancer/releases/download/tools/Truestancer.AutoStance.zip)
{% endhint %}

***

### The Interface

<div data-with-frame="true"><figure><img src="/files/XA6llkJI1TmU1If2VOk5" alt="" width="563"><figcaption><p>Main Page</p></figcaption></figure></div>

The tool contains 5 Main sections

1. **Entry Data**\
   At the entry data, is where you'll insert your Vehicles name, ***it should be the same as the .yft***<br>

   <div data-with-frame="true"><figure><img src="/files/V100aHvRx854sF4fl5Zl" alt="" width="544"><figcaption></figcaption></figure></div>

2. **Modkit And Variation ID**\
   \
   In this section, you will select what modkit type you want the stance settings to be installed with, and what variation.\
   \
   The variation id is 0 indexed, meaning it starts from 0, and is the order that you've created at carcols.\
   \
   So if you have declared ***partA, partB, partC*** for that specific modkit type, \
   **partA id is 0,** \
   **partB id is 1,** \
   **partC id is 2.**\
   \
   **Alternatively,** the variationId can also be found  as the list option of your part in a tuning menu -2.\
   So if it is the 4/15 **(4th part out of 15),&#x20;*****the id is 2.***\ <br>

   <div data-with-frame="true"><figure><img src="/files/4jQV60iKM2lbHVfsWXfv" alt="" width="536"><figcaption></figcaption></figure></div>

3. **Stance Settings**\
   Here is where you'll edit the stance settings you wish to be applied with that part, suspension raise, camber, etc.\
   \
   If an option is set at 0, it means it should be ignored and not applied, setting for example, just the width for the tyre profile, means the autostancer will just increase the width of the current tyre profile, without changin the rest.\
   \
   If also including a change in tyreprofile, the stock tyre measurements are required for restauring once the part is removed. You can check then using the in-game stance menu, which can be opened by pressing f11, if the "truestancer\_menu" resource is running in your FiveM server.\ <br>

   <div data-with-frame="true"><figure><img src="/files/EM0gFh8ENfUvdO5PGXcO" alt="" width="539"><figcaption></figcaption></figure></div>

4. **Current Data List**\
   \
   The list containing all items in the loaded project, you can click on the item to edit its properties, remove, or update it.<br>

   <div data-with-frame="true"><figure><img src="/files/cMPiHzK5eEnN7K3EGA1r" alt="" width="341"><figcaption></figcaption></figure></div>

5. **Main Buttons**\
   \
   These are the main buttons you'll use.\
   \
   Once the desired setup has been input, press add/update to add the part to the project.\
   Alternatively you can also remove the selected part from the list, and clear the form to it's default setting.\
   \
   Here is also where you'll be able to export the final .lua file, or even save your project as a json so you can share it with your team.<br>

   <div data-with-frame="true"><figure><img src="/files/xDqWcYYPPjf7qLQG5a1Y" alt=""><figcaption></figcaption></figure></div>

### Tool Usage

Now that you know the interface, simply do your desired changes and export your .lua file.\
\
Include it however you like on your FiveM vehicle resource and declare it in the fxmanifest.lua file like so:

```lua
fx_version 'cerulean'
games {'gta5'}

author 'GOM'
description 'GOM Styling'
version '3.0.0'

data_file 'VEHICLE_LAYOUTS_FILE' 'vehiclelayouts.meta'
data_file 'HANDLING_FILE' 'handling.meta'
data_file 'VEHICLE_METADATA_FILE' 'vehicles.meta'
data_file 'CARCOLS_FILE' 'carcols.meta'
data_file 'VEHICLE_VARIATION_FILE' 'carvariations.meta'
data_file "AUDIO_SYNTHDATA" "audioconfig/lgcl04gomstangrtr_amp.dat"
data_file "AUDIO_GAMEDATA" "audioconfig/lgcl04gomstangrtr_game.dat"
data_file "AUDIO_SOUNDDATA" "audioconfig/lgcl04gomstangrtr_sounds.dat"
data_file "AUDIO_WAVEPACK" "sfx/dlc_lgcl04gomstangrtr"


files {
    "audioconfig/*.dat151.rel",
  "audioconfig/*.dat54.rel",
  "audioconfig/*.dat10.rel",
  "sfx/**/*.awc",
  'vehiclelayouts.meta',
  'handling.meta',
  'vehicles.meta',
  'carcols.meta',
  'carvariations.meta',
}

client_script 'vehicle_names.lua'
client_script 'truestancer.lua' -- Our generated .lua from the tool.
lua54 'yes'
```

### Server Usage

Now, all you have to do is ensure your vehicle, and then restart the TrueStancer script.\
\
It's important that, if you're a server owner, at the load order, load the vehicles first, then the truestancer script.\
\
Any vehicle loaded after true stancer will not have the autoStancer feature integrated, requiring a restart of the script.

{% hint style="danger" %}
**We do not advise restarting TrueStancer in a live server enviroment, and instead recommend for it to be started/restarted with the server**
{% endhint %}


---

# Agent Instructions: 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://trueseries.gitbook.io/truestancer/tutorials/using-the-autostancer-feature.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.