Fusion modding · UNITS / AVIA / LAND/DOM

Buildings

A terrain building combines a resource record in dom.res, LAND/DOM settings, and a generic unit sheet. Houses, bunkers, casemates, and some fortifications use this system. Bridges use a different reader.

The configuration guide shows a change to an existing building. Building resources explains indices and graphics.

Settings files

File	Observed purpose
`<archive>/LAND/dom`	Base settings, common values, and includes.
`<archive>/LAND/descdom`	Settings for building indices.
`<archive>/LAND/defdom`	Included settings, such as sounds or fortifications. This file can also contain `obj` lines.
`<environment>/dom.res`	Graphics, palette, numeric class, and placement data.
`lang/UNITS/house`	Generic sheet for the `House` class.
`lang/UNITS/__testportal`	Generic sheet for the `Portal` class.

asien_unit/land/ uses a lowercase directory name. Some resources use the name DOM.RES. Keep the spelling used in your archive.

The engine reads the dom family file and its includes. It loads the resources before it applies settings to loaded types. A defdom file needs an include in the active dom file.

Selectors and order

level 0
HP default 500 500 500 500
HP type 2 1000 1000 1000 1000
HP obj 26 1333 1333 1333 1333

This example shows the three forms. The type line does not come from the current Fusion files.

Form	Scope
`key default values`	All loaded types in this family.
`key type class values`	Types with this numeric class in `dom.res`.
`key obj index values`	The type at this container index.
`level value`	A family setting, without a selector.

The engine applies all default lines, then all type lines, then all obj lines. It keeps the read order within each group, including included files. A later default line does not take priority over an obj line.

A later line in the same group can replace the same field. Armor and protection tables have separate entries for each damage type. Keep the necessary lines in each block.

The numeric resource class differs from seltype house or seltype bunker. It also differs from House in the UNITS registry. An obj index identifies a graphic type, not one building placed on the map.

Generic sheets and tunnels

house uses file none. Its graphics come from dom.res. During mission loading, resource classes below 6 select house. The other classes select __testportal.

A copy of house with a new identifier does not change this association. Common name, target, and attack properties remain in Identity and resources and Weapons and ammunition.

Tunnels use Portal when their resource class selects it. The generic sheet does not establish their capacity, links, travel, or combat rules.

Health and damage states

HP obj 0 1000 1000 1000 1000

The four numbers are health contributions. A building placed in state 0 starts with 4000 health here. In state 1, it starts with 3000 health. Transition thresholds add the contributions of the later states.

The reader consumes four values. A fifth value in a source file does not add a fifth state. The resource contains four graphic groups.

HP differs from health in UNITS. Also read the limits of armor and protection.

Reference limits

Code confirms the readers. Some delay units, garrison capacity rules, and exact bonus factors remain unknown. Examples keep Fusion values. They are not balance recommendations.

HS2Engine cover, hidden garrison, and medic mods can change the behavior. Record your DLL options for each trial. No interactive game or editor trial of this procedure was run here. See Sources and limits.

The classes and archives show where a property occurs. They do not guarantee support.

Buildings

Settings files

Selectors and order

Generic sheets and tunnels

Health and damage states

Reference limits

Source example

Source example

Source example

Source example

Source example

Source example

Source example

Source example

Source example

Source example

Source example

Source example

Source example

Source example

Source example

Source example

Source example

Source example

Source example

Source example