UnitsWML - Revision history

Mentos987: footprint race wide added

2026-08-02T18:00:45Z

footprint race wide added

← Older revision		Revision as of 18:00, 2 August 2026
Line 79:		Line 79:
	* '''[topic]''': describes extra help topics for this race.		* '''[topic]''': describes extra help topics for this race.
	* '''[trait]''': describes a trait for this race. See above for syntax.		* '''[trait]''': describes a trait for this race. See above for syntax.
			* '''footprints''': {{DevFeature1.19\|26}} (optional) pick what footprint group of images that units of this race should default to. E.g. ' footprints="swirling_pattern" ' will cause units to use images in the "..images\footsteps\swirling_pattern" folder. By default races will use the "..images\footsteps\default" footprint. If footprint is also assigned in the units cfg file then that will override this option for that specific unit.

	=== [resistance_defaults] ===		=== [resistance_defaults] ===

Shiki: /* [movetype] */ Link to new wiki page Movement_types

2026-06-14T13:59:35Z

[movetype]: Link to new wiki page Movement_types

← Older revision		Revision as of 13:59, 14 June 2026
Line 56:		Line 56:
	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>		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.

			There is a list with every mainline core [[Movement_types\|movetype]].

	=== [race] ===		=== [race] ===

Bssarkar: /* [trait] */ fix typo

2026-01-29T14:05:40Z

[trait]: fix typo

← Older revision		Revision as of 14:05, 29 January 2026
Line 27:		Line 27:
	=== [trait] ===		=== [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		* '''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.		* '''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.

Shiki: moved from 1.19.17 to 1.19.18

2025-12-15T21:23:43Z

moved from 1.19.17 to 1.19.18

← Older revision		Revision as of 21:23, 15 December 2025
Line 16:		Line 16:

	=== [abilities] ===		=== [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.		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] ===		=== [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.		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.

Bssarkar: /* [weapon_specials] */

2025-11-16T15:44:18Z

[weapon_specials]

← Older revision		Revision as of 15:44, 16 November 2025
Line 23:		Line 23:
	{{DevFeature1.19\|17}}		{{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] ===		=== [trait] ===

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

2025-11-16T15:43:54Z

[abilities]: Add [weapon_specials] vide #10691

← 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] ===

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

2025-11-03T03:31:54Z

= [abilities]: fixup links

← Older revision		Revision as of 03:31, 3 November 2025
Line 15:		Line 15:
	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] ==		=== [abilities] ===
	{{DevFeature1.19\|17}}		{{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] ===		=== [trait] ===

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

2025-11-03T03:29:24Z

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

← 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] ===

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

2025-11-02T04:11:26Z

[movetype]: emphasize special values

← Older revision		Revision as of 04:11, 2 November 2025
Line 38:		Line 38:
	** {{DevFeature1.15\|0}} '''flying''' always overrides the '''flies''' value, with the intention that '''flies''' will be deprecated.		** {{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]].		* '''[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\|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.)		* {{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>		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] ===		=== [race] ===

Bssarkar: /* [movetype] */ reword

2025-09-15T07:26:30Z

[movetype]: reword

← Older revision		Revision as of 07:26, 15 September 2025
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>		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 that ~~terrain~~.		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] ===		=== [race] ===