HowTo/Scenery/kuid-table - Revision history

Glt0145 at 00:20, 9 February 2022

2022-02-09T00:20:01Z

← Older revision		Revision as of 00:20, 9 February 2022
Line 1:		Line 1:

	== kuid-table ==		== kuid-table ==


	'''This tag is compulsory.'''		'''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.		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.		Now for what goes between the brackets are the kuids/kuid2s for any assets that are needed for you asset to work correctly. For each asset you are referencing the line needs to start with a number. 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.
Line 13:		Line 15:
	{		{

	<kuid:0000:00000>		0 <kuid:0000:00000>

	<kuid2:000:0000:1>		1 <kuid2:000:0000:1>

	}		}

Glt0145 at 23:55, 6 February 2022

2022-02-06T23:55:25Z

← Older revision		Revision as of 23:55, 6 February 2022
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.

Glt0145: /* kuid-table */

2022-02-05T03:45:11Z

kuid-table

← Older revision		Revision as of 03:45, 5 February 2022
Line 3:		Line 3:
	'''This tag is compulsory.'''		'''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. ~~Th close~~ 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.
Line 12:		Line 12:

	{		{

	<kuid:0000:00000>		<kuid:0000:00000>

	<kuid2:000:0000:1>		<kuid2:000:0000:1>

	}		}

Glt0145: Created page with " == 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 readabil..."

2022-02-05T03:43:36Z

Created page with " == 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 readabil..."

New page

== 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. Th close 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.

an example of a kuid-table.

kuid-table

{
<kuid:0000:00000>
<kuid2:000:0000:1>
}