Changes

Units are objects in Prism3d that have ability to inside SCS game engine. One of their core abilities is so they can be serialized or deserializedmaking it a perfect tool to give content creators a way to define various parts of the games.

* Name - units can be nameless or have some specified name . Unit names are divided into components which are 12-char tokens separated by dot - for example correct unit name will be <code>vehicle.dummy.truck</code> incorrect will be <code>vehicledummytruck</code> however in most cases you should not use them as in case engine detects two units with the same name it will fail so , in case some mod is using name <code>vehicle.dummy.truck</code> and you will also use this your mod will fail to load. To create nameless unit simply use dot as the prefix for your unit name for example <code>.my_mod.nameless.units</code>* Attributes - attributes is a are set of the data that unit can store, it can be number, text, other unit connection, set of them etc. Some units are failing in case they contain serialized some attribute that is no longer supported however some of them have special flag in the engine to allow loading not allowed attributes.

Units are stored in SII files. There are two versions of this file supported by the game engine textual : plain-text and binary however . However, only textual form the plain-text format is used for definitions.

=== Struture Structure ===

The magic mark - &ndash; used to check if the file is a real SII file or not.

<pre>SiiNUnitSiiNunit</pre>

attribute_tokenattribute_unit: TESTtest.unit attribute_vector3attribute_float3: (1.0, 1.0, 1.0)

The closing bracked bracket for the SiiNUnitSiiNunit

 It's always good to add one blank line at the end of the file.

You can also include the contents of other files into another. To do this you need to use using the SII preprocessor directives directive - <code>@include</code>. The contents of the included file will be read as if they were in the file itself. '''Example:'''<br />''some_file_using_include.sii''<pre>SiiNunit{example: doing.includes{ foo: &quot;bar&quot; over: 9000@include &quot;some_file_to_include.sui&quot;}}</pre>''some_file_to_include.sui:''<pre> ninjas: true</pre>''How the game &ldquo;sees&rdquo; some_file_using_include.sii:''<pre>SiiNunit{example: doing.includes{ foo: &quot;bar&quot; over: 9000 ninjas: true}}</pre>You may notice usage of the new extension - '''.sui'''. It's used for unit serialized files without magic mark <code>SiiNunit</code> that are included somewhere in different files. We recommend you also use this extension.

{{Note|The <code>@include</code> directive must appear at the beginning of a new line with no whitespace (space, tab, etc) before it. The following examples will '''Example:not'''work:<pre>SiiNunit{bad_examples: just.the.worst { foo: &quot;bar&quot; @include &quot;dont_get_too_attached_to_indents.sui&quot;

<pre> foo: @include &quot;some_file_to_includeyou_definitely_cannot_use_it_inline.sui&quot;}}</pre>You may notice usage of the new extension - '''.sui'''. It's used for unit serialized files without magic mark <code>SiiNUnit</code> that are included somewhere in different files. We recommend you also using this extension.}}

!width="19%"| Type!width="25%"| Value!width="55%"| Example! Notes

| float4x4placement| ?(x, y, z) (w; x, y, z)| attribute: (0, 0, 0) (1; 0, 0, 0)| ?

| ?attribute: 10|

| ?attribute: (10, 22)|

| ?attribute: (10, 22, 33)|

| ?attribute: (10, 22, 33, 44)|

|-| placement| ?| ?|-| placement_scale| ?| ?|-| placement_nonuniform| ?| ?|-| plane| ?| ?|-| aabox| ?| ?|-| token| x| attribute: value

| boolowner pointer (owner_ptr)

| attribute: true.some.nameless.unit| '''owner_ptr''' refers to unit defined within the same SiiNunit (eg. <brcode>attribute: false.trailer.tchassis</code>)

| unitlink pointer (link_ptr)

| attribute: mysome.named.unit| '''link_ptr''' refers to a named unit that is defined elsewhere (eg. <code>cabin_a.brand.model.cabin</code>)|-| resource_tie| "x"| attribute: "path/to/some/resource.pma"| '''resource_tie''' is typically used to bind animations to animated models. The syntax is the same as for 'string' type attributes.