Syntax and files

Files to know

The filename is the unit identifier. name sets the display name. file selects the graphics. These three names can differ.

One property per line

name "Tigre personnalise"
crew_unit dtankist
crew_number 5
movespeed 0.95 0.95
armor PIERCE 59 59 37 37 43 43

The engine separates values at spaces, tabs, commas, or = characters. Double quotes keep a text value together. A backslash stays as a normal character.

The game readers compare property keys after conversion to lowercase. This does not prove that all files or tools ignore letter case. Keep the spelling of existing resources and identifiers.

A pair does not always have the same meaning. Some properties use two limits. Others use a rate or a factor. Some readers ignore an extra value. Read the notes for each property.

Included files and disabled lines

#units\locomotive3
-fuelmax 2000

At the start of a line, # or @ tells the reader to read another file. It does not start a comment. The reader returns to the current file after the included file.

A dash in the first position disables the full line. Put the dash at the start of the line, with no space before it. Semicolons do not start general comments. Sound and animation readers can use them to end a reference.

This reference does not calculate the final sheet for an installation.

Game and editor

The game sheet reader skips a line when its first token starts with *. For this reader, * makes the line inactive. The next word does not need to be a known property.

The editor sheets also contain entries with a * prefix. The recent Fusion guide describes them as settings for the name, preview, and category. This explanation has not been checked against Mapeditor code or an editor test. An entry in a file does not prove that the editor uses it.

The Editor properties topic keeps these observations with this limit. They do not change behavior in the game.

*name "Tigre personnalise"
*picture tiger_edt.pck tiger_edt.col
*nationtype german tank

The *nationtype values match names in name/classify. Their use by the editor remains unknown. A registry class, such as Tank, differs from a category in this file, such as tank.

A unit can have copies in different environment archives. Check the applicable copies after a change. The archive loading order selects the files that the installation uses.

Encoding and checks

Keep the original encoding and CRLF line endings of copied sheets. The site examples use UTF-8 text for reading.

Some original files contain unclosed quotes or unusual sequences. An occurrence does not guarantee that the line works in the game.

The site values describe the Fusion files. They do not specify permitted ranges, limits, or defaults without engine evidence.

Building syntax

LAND/DOM adds a selector between the key and its values. Read the building reference before you copy a UNITS line. The engine applies default rules, then numeric class rules, then object index rules. Graphics come from dom.res.