UnitsWML - Revision history

Bssarkar: /* [trait] */ fix typo

2026-01-29T14:05:40Z

‎[trait]: fix typo

Shiki: moved from 1.19.17 to 1.19.18

2025-12-15T21:23:43Z

moved from 1.19.17 to 1.19.18

Bssarkar: /* [weapon_specials] */

2025-11-16T15:44:18Z

‎[weapon_specials]

Bssarkar: /* [abilities] */ Add [weapon_specials] vide #10691

2025-11-16T15:43:54Z

‎[abilities]: Add [weapon_specials] vide #10691

Bssarkar: /* = [abilities] */ fixup links

2025-11-03T03:31:54Z

‎= [abilities]: fixup links

Bssarkar: /* Subtags of [units] */ [abilities] (PR #10644)

2025-11-03T03:29:24Z

‎Subtags of [units]: [abilities] (PR #10644)

Bssarkar: /* [movetype] */ emphasize special values

2025-11-02T04:11:26Z

‎[movetype]: emphasize special values

Bssarkar: /* [movetype] */ reword

2025-09-15T07:26:30Z

‎[movetype]: reword

Bssarkar: /* [movetype] */ Explain missing archetype case

2025-09-15T07:16:23Z

‎[movetype]: Explain missing archetype case

Laela: /* [terrain_defaults] */ 9676

2025-03-20T11:32:13Z

‎[terrain_defaults]: 9676

@@ Line 27: / Line 27: @@
 === [trait] ===
-The '''[trait]''' tag describes a trait. When it appears in the '''[units]''' toplevel, it describes a global trait, and all races with the attribute '''ignore_global_traits=no''' will have this trait.; it may also appear in other places.
+The '''[trait]''' tag describes a trait. When it appears in the '''[units]''' toplevel, it describes a global trait, and all races with the attribute '''ignore_global_traits=no''' will have this trait. It may also appear in other places.
 * '''id''': unique identifier; needed for random trait generation to work properly
 * '''availability''': describes whether a trait is "musthave" for a race/unit type or is available to "any" unit, including leaders. The default is for a trait to only be available to nonleaders. Currently "any" should not be used for traits available in multiplayer. It can be used for campaign specific traits.

@@ Line 16: / Line 16: @@
 === [abilities] ===
-{{DevFeature1.19|17}}
+{{DevFeature1.19|18}}
 A registry for Abilities. Abilities can be defined here in the usual way via [[AbilitiesWML]]. Any such ability can be then added to '''[unit_type]''' or '''[effect]apply_to=new_ability''' by mentioning its '''unique_id''' (or '''id''' if unique_id is undefined) without the need to include the full ability definition.
 === [weapon_specials] ===
-{{DevFeature1.19|17}}
+{{DevFeature1.19|18}}
 A registry for Weapon Specials. Weapon Specials can be defined here in the usual way via [[AbilitiesWML]]. Any such weapon special can then be added to '''[unit_type][attack]''' or '''[effect]apply_to=new_attack/attack''' by mentioning its '''unique_id''' (or '''id''' if unique_id is undefined) without the need to include the full ability definition.

@@ Line 23: / Line 23: @@
 {{DevFeature1.19|17}}
-A registry for Weapon Specials. Weapon Specials can be defined here in the usual way via [[AbilitiesWML]]. Any such weapon special can then be added to '''[unit_type][attack]''' or '''[effect]apply_to=new_attack''' by mentioning its '''unique_id''' (or '''id''' if unique_id is undefined) without the need to include the full ability definition.
+A registry for Weapon Specials. Weapon Specials can be defined here in the usual way via [[AbilitiesWML]]. Any such weapon special can then be added to '''[unit_type][attack]''' or '''[effect]apply_to=new_attack/attack''' by mentioning its '''unique_id''' (or '''id''' if unique_id is undefined) without the need to include the full ability definition.
 === [trait] ===

← Older revision		Revision as of 15:43, 16 November 2025
Line 19:		Line 19:

	A registry for Abilities. Abilities can be defined here in the usual way via [[AbilitiesWML]]. Any such ability can be then added to '''[unit_type]''' or '''[effect]apply_to=new_ability''' by mentioning its '''unique_id''' (or '''id''' if unique_id is undefined) without the need to include the full ability definition.		A registry for Abilities. Abilities can be defined here in the usual way via [[AbilitiesWML]]. Any such ability can be then added to '''[unit_type]''' or '''[effect]apply_to=new_ability''' by mentioning its '''unique_id''' (or '''id''' if unique_id is undefined) without the need to include the full ability definition.
		+
		+	=== [weapon_specials] ===
		+	{{DevFeature1.19\|17}}
		+
		+	A registry for Weapon Specials. Weapon Specials can be defined here in the usual way via [[AbilitiesWML]]. Any such weapon special can then be added to '''[unit_type][attack]''' or '''[effect]apply_to=new_attack''' by mentioning its '''unique_id''' (or '''id''' if unique_id is undefined) without the need to include the full ability definition.

	=== [trait] ===		=== [trait] ===

@@ Line 15: / Line 15: @@
 In a '''[units]''' tag, a '''[unit_type]''' tag defines a unit type.
-=== [abilities] ==
+=== [abilities] ===
 {{DevFeature1.19|17}}
-A registry for Abilities. Abilities can be defined here in the usual way via [AbilitiesWML https://wiki.wesnoth.org/AbilitiesWML]. Any such ability can be then added to [unit_type] or [effect]apply_to=new_ability by mentioning its unique_id (or id if unique_id is undefined) without the need to include the full ability definition.
+A registry for Abilities. Abilities can be defined here in the usual way via [[AbilitiesWML]]. Any such ability can be then added to '''[unit_type]''' or '''[effect]apply_to=new_ability''' by mentioning its '''unique_id''' (or '''id''' if unique_id is undefined) without the need to include the full ability definition.
 === [trait] ===

← Older revision		Revision as of 03:29, 3 November 2025
Line 14:		Line 14:

	In a '''[units]''' tag, a '''[unit_type]''' tag defines a unit type.		In a '''[units]''' tag, a '''[unit_type]''' tag defines a unit type.
		+
		+	=== [abilities] ==
		+	{{DevFeature1.19\|17}}
		+
		+	A registry for Abilities. Abilities can be defined here in the usual way via [AbilitiesWML https://wiki.wesnoth.org/AbilitiesWML]. Any such ability can be then added to [unit_type] or [effect]apply_to=new_ability by mentioning its unique_id (or id if unique_id is undefined) without the need to include the full ability definition.

	=== [trait] ===		=== [trait] ===

@@ Line 38: / Line 38: @@
 ** {{DevFeature1.15|0}} '''flying''' always overrides the '''flies''' value, with the intention that '''flies''' will be deprecated.
 * '''[special_note]''' {{DevFeature1.15|14}} note=Translatable string, which can be set if there’s something special about this movetype. It will be displayed in the unit's help page. For typical movetypes this is not set. An example are horses with the ''mounted'' movetype. See also [[UnitTypeWML#Special_Notes]].
-* {{anchor|resistance|'''[resistance]'''}}: describes how much damage the unit takes from different types of attacks. The attribute '''''type''=''resistance''''' makes the unit receive ''resistance'' percent of damage, or resist '''100-resistance''' percent of damage from attacks with '''type=''type'''''. So for example, a resistance of fire=110 means, this unit will receive 110% of damage, or have a resistance of -10% as displayed in-game. A value of fire=0 would mean, the unit receives no damage and therefore has a resistance of 100%.<br> The available attack types in mainline are blade, pierce, impact, fire, cold, and arcane.
+* {{anchor|resistance|'''[resistance]'''}}: describes how much damage the unit takes from different types of attacks. The attribute '''''type''=''resistance''''' makes the unit receive ''resistance'' percent of damage, or resist '''100-resistance''' percent of damage from attacks with '''type=''type'''''. So for example, a resistance of fire=110 means, this unit will receive 110% of damage, or have a resistance of -10% as displayed in-game. A value of fire=0 would mean, the unit receives no damage and therefore has a resistance of 100%.<br> The available attack types in mainline are ''blade'', ''pierce'', ''impact'', ''fire'', ''cold'', and ''arcane''.
 * {{anchor|movement_costs|'''[movement_costs]'''}}: describes how fast the unit moves on different terrains. The attribute '''''terrain''=''cost''''' means that the unit will need to use ''cost'' move points to move onto that ''terrain''.
 * {{anchor|vision_costs|'''[vision_costs]'''}}: describes how far the unit clears fog and shroud on different terrains. The attribute '''''terrain''=''cost''''' means that the unit will need to use ''cost'' vision points to view into that ''terrain''. (If not specified for a particular terrain, the vision cost defaults to the movement cost.)
@@ Line 45: / Line 45: @@
 The available keys for the '''[movement_costs]''', '''[vision_costs]''', '''[jamming_costs]''' and '''[defense]''' tags are the '''id'''s of archetype terrains (those not aliased to any other terrain, see [[TerrainWML]]).<br>
-In mainline that encompasses deep_water, shallow_water, reef, swamp_water, flat, sand, forest, hills, mountains, village, castle, cave, frozen, unwalkable, fungus, and impassable. If a particular archetype is not mentioned in a movetype, it means a unit with that movetype cannot move to a terrain with that archetype.
+In mainline that encompasses ''deep_water'', ''shallow_water'', ''reef'', ''swamp_water'', ''flat'', ''sand'', ''forest'', ''hills'', ''mountains'', ''village'', ''castle'', ''cave'', ''frozen'', ''unwalkable'', ''fungus'', and ''impassable''. If a particular archetype is not mentioned in a movetype, it means a unit with that movetype cannot move to a terrain with that archetype.
 === [race] ===

@@ Line 87: / Line 87: @@
 The '''[terrain_defaults]''' tag allows you to add costs and defenses for custom terrain types to already-defined movetypes (such as core movetypes).
 * '''id''': The '''id=''' attribute of the terrain type you want to apply cost and defense defaults for.
-* Subtags are used to specify the values using the same syntax as [resistance_defaults] - an optional default key, and subsequent keys which are movetype names. As with [resistance_defaults], you can use [[Wesnoth Formula Language|formulas]] if you enclose them in parentheses (but with no preceding dollar sign <code>$</code>).
+* Subtags are used to specify the values using the same syntax as [resistance_defaults] - an optional default key, and subsequent keys which are movetype names. As with [resistance_defaults], you can use [[Wesnoth Formula Language|formulas]] if you enclose them in parentheses (but with no preceding dollar sign <code>$</code> or whitespace).
 * Short names for the subtags are '''[movement]''', '''[jamming]''', '''[vision]''', and '''[defense]'''.
 * Long names for the subtags are '''[movement_costs]''', '''[vision_costs]''', '''[jamming_costs]''', and '''[defense]'''.