Difference between revisions of "Custom cars"
Jump to navigation
Jump to search
DiRTyDRiVER (talk | contribs) m |
DiRTyDRiVER (talk | contribs) |
||
Line 39: | Line 39: | ||
* create a Folder “cars” in Folder “cfg” | * create a Folder “cars” in Folder “cfg” | ||
* create exampleCar.json-File in Folder “cars”, with the following content: | * create exampleCar.json-File in Folder “cars”, with the following content: | ||
+ | <source lang=json> | ||
+ | { | ||
+ | "raceNumber": 12, | ||
+ | "carModelType": 3, | ||
+ | "useEnduranceKit": 1, | ||
+ | "cupCategory": 0, | ||
+ | "skinTemplateKey": 103, | ||
+ | "sponsorId": 15, | ||
+ | "auxLightKey": 1, | ||
+ | "auxLightColor": 67, | ||
+ | "skinColor1Id": 345, | ||
+ | "skinColor2Id": 200, | ||
+ | "skinColor3Id": 125, | ||
+ | "skinMaterialType1": 1, | ||
+ | "skinMaterialType2": 3, | ||
+ | "skinMaterialType3": 1, | ||
+ | "rimColor1Id": 345, | ||
+ | "rimColor2Id": 200, | ||
+ | "rimMaterialType1": 1, | ||
+ | "rimMaterialType2": 1, | ||
+ | "teamName": "My Team", | ||
+ | "displayName": "", | ||
+ | "competitorName": "" | ||
+ | } | ||
+ | |||
+ | </source> |
Revision as of 10:37, 19 October 2019
create File “entrylist.json”
create File “entrylist.json” in Folder “cfg”, with the following content:
{ "entries":[
{ "drivers": [
{ "playerID": "S765611xxxxxxxxxx1"}
],
"overrideDriverInfo": 0,
"overrideCarModelForCustomCar": 1,
"customCar": "exampleCar.json",
},
{ "drivers": [
{ "playerID": "S765611xxxxxxxxxx2"}
],
"overrideDriverInfo": 0,
"overrideCarModelForCustomCar": 1,
"customCar": "exampleCar2.json",
}
]
}
... | Note |
---|---|
playerID | SteamID from Driver, insert an "S" in front of it |
more properties | For further information see in the "Server Admin Manual" to: \Steam\steamapps\common\Assetto Corsa Competizione\server in VI. Entry List |
overrideDriverInfo | If set to 1, the driver’s name and category will be overridden by what is setup in the entry list. If set to 0, it’s up to the client joining. |
overrideCarModelForCustomCar | If "customCar" is used, this setting will apply the car model configured if the value is set to 1 ( which is the default ). If set to 0, all values except the "carModelType" are applied, so the user is free to pick a car but while team name and appearance will be applied |
customCar | If set to a filename, the car, team and appearance will be used no matter what the user chose ( Exception: “overrideCarModelForCustomCar” ). This is useful for leagues and events, where we want consistent car appearance and the chosen car model for the corresponding driver/team. The custom car file has to be located in a “cars” folder next to the entrylist.json ( also works for centralEntryListPath ). Leave blank ( “” = default ) to let the user chose the car via car selection UI. |
create File “exampleCar.json”
- create a Folder “cars” in Folder “cfg”
- create exampleCar.json-File in Folder “cars”, with the following content:
{
"raceNumber": 12,
"carModelType": 3,
"useEnduranceKit": 1,
"cupCategory": 0,
"skinTemplateKey": 103,
"sponsorId": 15,
"auxLightKey": 1,
"auxLightColor": 67,
"skinColor1Id": 345,
"skinColor2Id": 200,
"skinColor3Id": 125,
"skinMaterialType1": 1,
"skinMaterialType2": 3,
"skinMaterialType3": 1,
"rimColor1Id": 345,
"rimColor2Id": 200,
"rimMaterialType1": 1,
"rimMaterialType2": 1,
"teamName": "My Team",
"displayName": "",
"competitorName": ""
}