Understanding Prices

To understand the configuration of prices, you must first know the priority of their recognition and examples of use.


Database

The highest priority, if you use the Config.LoadPricesFromDatabase option and a price for a specific model is obtained from the database, this price will be the most important for tuning.


By model

Getting the price by model in Config.Vehicles is the second point of priority, you can configure this option in two ways, a more extensive one defining the price for cosmetic, mechanical and extra options, and a simple one that will calculate to each part a percentage of one price.

Extensive Way

In the Extensive Way, you must define three options in the table.

Options that fall under: mechanicals: Engine, Brakes, Transmission, Suspension, Armor, Turbo extras: Paint Type Primary, Paint Type Secondary, Xenon Color, Horn, Livery cosmetics: all the rest not mentioned above

["italigtb2"] = {
    mechanicals = 500000,
    cosmetics = 300000, 
    extras = 130000, 
},
Simple Way

In the Simple Way, you only have to define the amount of the vehicle.

["italigtb2"] = 300000,


By class

Getting the price by vehicle class in Config.VehiclesPricesByClass, is the third point in priority, you can also configure this option in two ways like the above - extensive and simple.

Extensive Way

In the Extensive Way, you must define three options in the table.

Options that fall under: mechanicals: Engine, Brakes, Transmission, Suspension, Armor, Turbo extras: Paint Type Primary, Paint Type Secondary, Xenon Color, Horn, Livery cosmetics: all the rest not mentioned above

Simple Way

In the Simple Way, you only have to define the amount of the vehicle.


By default price

If none of the above options apply to the vehicle you are currently trying to tune, then it will load a fixed price from Config.DefaultVehiclePrice

Last updated

Was this helpful?