Default is male (unless random_gender is set to "yes"), but if the unit has only a female variant it will be female. gender: can be set to male or female to designate the gender of the unit.WML should therefore be structured in such a way that no two units in existence ever end up with the same ID. (The one instance when an id is displayed to the player is when the leader's id is used as the default for a side's current_player attribute.) Note: While it IS technically possible to create multiple units with the same ID, doing so may produce unpredictable results in many cases. In older versions, the description attribute specified a unique ID. If not specified, a random one will be generated for the unit to ensure that each unit has a unique id attribute (as will happen when a unit is recruited normally). This is (usually) not displayed to the player, but is to be used only for identifying and filtering units. Defaults to 1, except when the tag appears inside a, in which case the unit always belongs to that side, and this key is ignored. It has to be an existing side, even if the unit is created in a variable. This is likely of little use to WML authors it is automatically generated when needed by the game (to keep track of some s). parent_type: overrides type if this is present.variation: the of the as which the unit will appear.The following keys and tags describe the unit itself, and will persist with the unit (though some may change automatically when the unit advances): Finally, there are some keys to set certain one-time options for how the unit will be initially created, which will not persist beyond initial creation. This contains keys and tags which describe the unit's persistent data, as well as certain state variables which will also persist with the unit but will change frequently as gameplay progresses. can be used inside ( SideWML) for units present at start of the scenario, or as DirectActionsWML for units created during the game. However it takes many of the same keys and thus can generally override the inherited properties from the associated. It is different from the in, which describes a class of units. The tag describes a single unit on the map or in memory, for example Konrad.
0 kommentar(er)
