# Advanced Strategic Command

documentation

## MakeTank

This is a description on how to create your own pictures of vehicles.

For a documentation of the different fields that define a vehicle type take a look at the tutorial on importing Battle Isle graphics.

When creating your own graphics the file `tools\hexpics\hexfield.pcx` should be used as the basis and the vehicle has to be painted in the hexagon there.

The colors 16 - 23 (red colortone) will be shifted depending on the player who owns the vehicle. For the second player these colors will be shifted to 24 - 31 and so on. The color #255 is transparent so fill the remaining hexagon with this color when finished.

## Defining unit sets

You can group several vehicles together to form a unitset. In the mapeditor, you can enable and disable unitsets to make the selection of units easier. You can also define transformations that replace all units on a map by others. This is useful if you want to play a map with a different unit set than the one that is originally used by the map.

To define a unit set, you must create a unitset definition file, which is a plain text file with the extension `.set` . I suggest that you put all vehicles together with this unitset definition file into a single container (see mount for more information).

Here is an example for a unitset definition file:

> `#V2#
> NAME=Standard Unitset
> ID=0-800,900,920-930,950
> MAINTAINER=Martin Bickel (martin@asc-hq.org)
> INFORMATION=This unitset is part of the standard ASC data package which can be obtained from http://www.asc-hq.org
> ACTIVE=1
> TRANSFORMATION=Example transformation;24,1840;25,1872;26,1805;27,1839;28,1878;29,1845;30,1834;31,1859;32,1821;33,1862;34,1810
> TRANSFORMATION=Another transformation;77,1877;78,1878;79,1879;1000,1822;1001,1829;1002,1806
> `

The first line must always be `#V2#`. This is to tell ASC that this is the second revision of the unitset definition file format. It is still possible to use the files with the old format, but if you create a new one use this new format.

Each of the following lines starts with a keyword, which must be UPPERCASE, an equals sign and some data. The order in which the properties are defined is not relevant.

NAME
  The name of the unitset. This field is required.
ID
  The IDs of the units that form the unitset. This field is required.
MAINTAINER
  Some information about the person who maintains the unitset. This field is optional.
INFORMATION
  Some information about the unitset. The internet address where new versions can be optained is useful here. This field is optional.
ACTIVE
  Possible values are `0` and `1` . The default which is used if this field is not specified is `1` . If this variable is `0`, the units are not visible in the Vehicle Type Information Window in ASC. In the mapeditor's Setup Unit Filter dialog the default for each unitset is this variable. That means, even if a unitset is marked inactive, you can activate it with just three mouse clicks and see all units in it. There is no way to hide units completely. This field is optional.
TRANSFORMATION
  The field consists of the transformations name, a semicolon ( `;` ) and a list of pairs of IDs. The first number is the ID of the unittype that will be replaced by the unittype with the second ID when this transformation is executed. In the above example, all units with ID 24 are replaced by units with ID 1840, all units with ID 25 are replaced by units with ID 1872, etc. You may define any number of transformations. Each transformation must be in a single line. These fields are optional.
FILTERBUILDINGS
  The field is either zero or non-zero. If non-zero, buildings that are withing the range of IDs assigned to this unitset are not selectable too when this unitset is deactivated. Default is 0. This field is optional.