HowTo/Scenery/kuid
(→KUID) |
|||
| (4 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
== KUID == | == KUID == | ||
| + | |||
| + | '''This tag is compulsory.''' | ||
| + | |||
| + | |||
Every config file must have a KUID. This is a unique number that Trainz uses to identify the asset. They can be one of two forms. | Every config file must have a KUID. This is a unique number that Trainz uses to identify the asset. They can be one of two forms. | ||
| − | kuid < | + | kuid <kuid:User_ID:Content_ID:> |
| − | This | + | This kuid was the original used by the early trainz versions. it consist of there parts |
| − | The word " | + | The word "kuid" which identifies what it is. |
| − | The first | + | The first User_ID is your used ID number that you would have been given when you first registered your Trainz |
| − | The second | + | The second Version_ID is a unique identifier that you create for your asset. Each asset you create must have it's own unique identifier. It easiest to keep track of your identifiers in a spreadsheet |
If you use this format for you config file and update to the asset would need to have a new unique identifier. | If you use this format for you config file and update to the asset would need to have a new unique identifier. | ||
| Line 20: | Line 24: | ||
or | or | ||
| − | kuid <KUID2: | + | kuid <KUID2:User_ID:Content_ID:Version_ID> |
This style of KUID has been used in all but the first few Trainz versions. It has a few advantages over the original. | This style of KUID has been used in all but the first few Trainz versions. It has a few advantages over the original. | ||
| − | The word " | + | The word "kuid2" which identifies what it is and tells Trainz to expect three sets of numbers |
| − | The first | + | |
| − | The second | + | The first User_ID is your used ID number that you would have been given when you first registered your Trainz |
| − | The third is the version number. These normally start with version | + | |
| + | The second Content_ID is a unique number that you create for your asset. Each asset you create must have it's own unique number. It easiest to keep track of your identifiers in a spreadsheet. | ||
| + | |||
| + | The third Version_ID is the version number. These normally start with version 0. If you create an update to an asset the next number in sequence would be used example 1. Version numbers allow Trainz to identify the latest version your asset. When making an update to an object an "obsolete" container in your config file will contain the obsolete KUID numbers. See the page for obsolete from the scenery config page. | ||
| − | An example of the line in your config file for the KUID would be kuid <KUID2:0000:00000: | + | An example of the line in your config file for the KUID would be kuid <KUID2:0000:00000:0>. The next one KUID for an updated asset would be <KUID2:0000:00000:1> |
Either style of these KUIDS can be used but it would be recommended to use the second one at is now the Trainz standard for KUIDs | Either style of these KUIDS can be used but it would be recommended to use the second one at is now the Trainz standard for KUIDs | ||
Latest revision as of 09:45, 9 February 2022
[edit] KUID
This tag is compulsory.
Every config file must have a KUID. This is a unique number that Trainz uses to identify the asset. They can be one of two forms.
kuid <kuid:User_ID:Content_ID:>
This kuid was the original used by the early trainz versions. it consist of there parts
The word "kuid" which identifies what it is.
The first User_ID is your used ID number that you would have been given when you first registered your Trainz
The second Version_ID is a unique identifier that you create for your asset. Each asset you create must have it's own unique identifier. It easiest to keep track of your identifiers in a spreadsheet
If you use this format for you config file and update to the asset would need to have a new unique identifier.
The text in you config file for this type of KUID has to have the chevrons <> at the start and finish the text string. without them the trainz importer will throw an error and example of the line in your config file for the KUID would be kuid <KUID:000:0000>
or
kuid <KUID2:User_ID:Content_ID:Version_ID>
This style of KUID has been used in all but the first few Trainz versions. It has a few advantages over the original. The word "kuid2" which identifies what it is and tells Trainz to expect three sets of numbers
The first User_ID is your used ID number that you would have been given when you first registered your Trainz
The second Content_ID is a unique number that you create for your asset. Each asset you create must have it's own unique number. It easiest to keep track of your identifiers in a spreadsheet.
The third Version_ID is the version number. These normally start with version 0. If you create an update to an asset the next number in sequence would be used example 1. Version numbers allow Trainz to identify the latest version your asset. When making an update to an object an "obsolete" container in your config file will contain the obsolete KUID numbers. See the page for obsolete from the scenery config page.
An example of the line in your config file for the KUID would be kuid <KUID2:0000:00000:0>. The next one KUID for an updated asset would be <KUID2:0000:00000:1>
Either style of these KUIDS can be used but it would be recommended to use the second one at is now the Trainz standard for KUIDs
