HowTo/Scenery/kuid-table: Difference between revisions

From TrainzOnline
Jump to navigationJump to search
Glt0145 (talk | contribs)
Glt0145 (talk | contribs)
No edit summary
Line 5: Line 5:
This is a container tag, meaning it is followed by curly brackets. The opening bracket should be on the next line for readability purposes. The closing bracket is best on the next line after the final entry. Again for readability purposes.
This is a container tag, meaning it is followed by curly brackets. The opening bracket should be on the next line for readability purposes. The closing bracket is best on the next line after the final entry. Again for readability purposes.


Now for what goes between the brackets are the kuids/kuid2s for any assets that are needed for you asset to work correctly.
Now for what goes between the brackets are the kuids/kuid2s for any assets that are needed for you asset to work correctly. These may be some you created yourself or referencing one made by another asset developer.  


an example of a kuid-table.
an example of a kuid-table.

Revision as of 23:55, 6 February 2022

kuid-table

This tag is compulsory.

This is a container tag, meaning it is followed by curly brackets. The opening bracket should be on the next line for readability purposes. The closing bracket is best on the next line after the final entry. Again for readability purposes.

Now for what goes between the brackets are the kuids/kuid2s for any assets that are needed for you asset to work correctly. These may be some you created yourself or referencing one made by another asset developer.

an example of a kuid-table.

kuid-table

{

<kuid:0000:00000>

<kuid2:000:0000:1>

}