It contains list of archetypes CBaseArchetypeDef and/or MLO archetypes CMloArchetypeDef

Number in this value means how far will be visible object in game. In this example object will be visible until 1000 unit coord on any axis (x,y,z) if you will be at distance more than 1000 unit (on any direction x,y,z) then object will dissapear.

Flag determines how object will affect in game. For example:
<flags value="32"/> for objects with embedded collision
<flags value="0"/> default for objects without embedded collision
<flags value="604110848"/> for doors
<flags value="537001984"/> for doors
<flags value="67239936"/> for doors
<flags value="8192"/> mostly for emmisive and ground (dont cast shadows)
<flags value="8192"/> mostly for blend ground (dont cast shadow)
<flags value="8190"/> cast only shadow - object invisible


This section will update in future with more researched flags.

Its related to #typ flag! (for example <specialAttribute value="5"/> will have different effect in different #typ flags.
Mainly its used for doors and determine how doors will open, for example:
Using 67239936 for flag:

<specialAttribute value="5"/> doors will open up/down 90 degrees (like garage door)
<specialAttribute value="4"/> doors will slides (left<->right)
<specialAttribute value="7"> normal way of opening door (pushed by player)

This is boundary box values - two pints in box in min and max:

Too small values in bbmin/max will make object flickering in game, disappearing on camera angles or even invisible:

You can generate it using Neos7 3dsmax script (map helper)
bbmin/max must be big enough to match object size.

This is used in texture parenting - on which distance high resolution texture will switch to low resolution.
Explanation how to set texture parenting check _manifest.

If your object use any external texture from ytd then you put ytd name like this:
<textureDictionary>ytd name here</textureDictionary>
And if your object got only embedded textures and dont use any from ytd then you leave it like this:
<textureDictionary/>

Its used only when object got animation and uses clip dictionaries (#cd) then you put name of ycd like this:
<clipDictionary>ycd name here</clipDictionary>
When object dont have any animation you leave it like this:
<clipDictionary/>

When definied object is inside drawable dictionary (.#dd) then you put name of this dictionary like this:
<drawableDictionary>ydd name here</drawableDictionary>
in other cases you leave it empty:
<drawableDictionary/>

In most cases its used for LODs

When your object got embedded collision then you put here name of object or name of RPF inside which is that object (both ways works second one is good for neos script at many objects)

<physicsDictionary>name of object with embedded collision here</physicsDictionary>
or
<physicsDictionary>name of RPF inside which is object with embedded collision</physicsDictionary>

If your object dont have any collision or its uses static one then you leave it empty:
<physicsDictionary/>

You can choose type of asset:
ASSET_TYPE_UNINITIALIZED
ASSET_TYPE_FRAGMENT
ASSET_TYPE_DRAWABLE
ASSET_TYPE_DRAWABLEDICTIONARY
ASSET_TYPE_ASSETLESS

But by default you can choose between two :
ASSET_TYPE_DRAWABLE - for normal props
or
ASSET_TYPE_DRAWABLEDICTIONARY for props inside drawable dictionary (.#dd)

Extensions are used for many cool things like ladders, spawning peds, adding water,fire or other FX effects, lights, sounds ect...

Here i will give two examples adding spawning point for ped and adding fire to object:

1. Spawning ped you need to add into extensions:

2. Adding fire to object you need to add into extensions:

It defines at which hours archetype can be visible in game.

Its binary flag where each bit represent specified hour of day plus bit #24 must be always 1, otherway whole timeFlag will not work: