MovementZone - Revision history

ZivDero: Strong is not a MovementZone, but a testid hallucination

2025-10-18T01:55:23Z

Strong is not a MovementZone, but a testid hallucination

← Older revision		Revision as of 03:55, 18 October 2025
Line 49:		Line 49:
	!WaterBeach [[Image:Ra2small.png]],{{yro}}		!WaterBeach [[Image:Ra2small.png]],{{yro}}
	\|Like Water but adds Beach cells to pathfinding. Worth noting that RA2 [[TileSets]] don't make use of this properly, and a lot of terrain editing will be required to actually make useable Beach.		\|Like Water but adds Beach cells to pathfinding. Worth noting that RA2 [[TileSets]] don't make use of this properly, and a lot of terrain editing will be required to actually make useable Beach.
	\|-
	~~!Strong [[Image:Ra2small.png]],{{yro}}~~
	~~\|Currently unknown behaviour.~~
	\|}		\|}

ATHSE at 04:53, 19 April 2025

2025-04-19T04:53:28Z

← Older revision		Revision as of 06:53, 19 April 2025
Line 48:		Line 48:
	\|-		\|-
	!WaterBeach [[Image:Ra2small.png]],{{yro}}		!WaterBeach [[Image:Ra2small.png]],{{yro}}
	\| ~~???~~		\|Like Water but adds Beach cells to pathfinding. Worth noting that RA2 [[TileSets]] don't make use of this properly, and a lot of terrain editing will be required to actually make useable Beach.
	\|-		\|-
	!Strong [[Image:Ra2small.png]],{{yro}}		!Strong [[Image:Ra2small.png]],{{yro}}
	\|~~???~~		\|Currently unknown behaviour.
	\|}		\|}

MarkJFox: 17 revisions imported

2025-03-31T19:59:35Z

17 revisions imported

← Older revision	Revision as of 21:59, 31 March 2025
(No difference)

en>Testid123 at 14:45, 3 February 2025

2025-02-03T14:45:57Z

← Older revision		Revision as of 16:45, 3 February 2025
Line 44:		Line 44:
	If a different {{f\|MovementZone}} is set the unit will only dig if both origin and target locations can be dug into; else it'll drive and only re-consider digging after a complete and absolute stop and ''then'' giving a new order manually. If persuaded to get underground then given a new order it'll try going to new target location, and if it can't dig out of it it'll look for closest exit only after it reaches/gets directly below the target.		If a different {{f\|MovementZone}} is set the unit will only dig if both origin and target locations can be dug into; else it'll drive and only re-consider digging after a complete and absolute stop and ''then'' giving a new order manually. If persuaded to get underground then given a new order it'll try going to new target location, and if it can't dig out of it it'll look for closest exit only after it reaches/gets directly below the target.
	\|-		\|-
	!Water		!Water [[Image:Ra2small.png]],{{yro}}
	\|When pathfinding, considers only water as passable.		\|When pathfinding, considers only water as passable.
	\|-		\|-
	!WaterBeach		!WaterBeach [[Image:Ra2small.png]],{{yro}}
	\| ???		\| ???
	\|-		\|-
			!Strong [[Image:Ra2small.png]],{{yro}}
			\|???
	\|}		\|}

en>DeathFish at 05:51, 2 January 2023

2023-01-02T05:51:51Z

← Older revision		Revision as of 07:51, 2 January 2023
Line 21:		Line 21:
	Units with Subterranean [[Locomotor]] and Crusher MovementZone will only dig in if there are 11 tiles between unit destination. Those tiles were Clear tiles.		Units with Subterranean [[Locomotor]] and Crusher MovementZone will only dig in if there are 11 tiles between unit destination. Those tiles were Clear tiles.
	\|-		\|-
	!CrusherAll		!CrusherAll{{yro}}
	\|Same as '''Crusher''', additionally assumes that it can crush any mobile object, as well as walls.<sup>[[#Notes\|2]]</sup>		\|Same as '''Crusher''', additionally assumes that it can crush any mobile object, as well as walls.<sup>[[#Notes\|2]]</sup>
	\|-		\|-

en>Crimsonum at 10:11, 19 April 2022

2022-04-19T10:11:24Z

← Older revision		Revision as of 12:11, 19 April 2022
Line 1:		Line 1:
	{{flag\|name=MovementZone\|files=rules(md).ini\|values=special strings\|default=<tt>Normal</tt>\|types=[[InfantryTypes]], [[VehicleTypes]], [[AircraftTypes]], [[BuildingTypes]] (to the same extent as [[Locomotor]]s do) \|ts=yes\|fs=yes\|ets=yes\|ra2=yes\|yr=yes\|rp=yes}}.		{{flag\|name=MovementZone\|files=rules(md).ini\|values=special strings\|default=<tt>Normal</tt>\|types=[[InfantryTypes]], [[VehicleTypes]], [[AircraftTypes]], [[BuildingTypes]] (to the same extent as [[Locomotor]]s do) \|ts=yes\|fs=yes\|ets=yes\|ra2=yes\|yr=yes\|rp=yes}}
	~~[[SpeedType]] is what actually allows or disallows a unit to move over [[TileType}}.~~		MovementZone says where the unit is allowed to go and helps the [[AI]] pathfinding routines. The possible values it takes are:
			{\| align="center" cellpadding="6" class="wikitable table_descrowdesccol"
	MovementZone says where is the unit allowed to go and helps the [[AI]] pathfinding routines. The possible values it takes are:
	{\| align="center" cellpadding="6" class="table_descrowdesccol"
	!''MovementZone''		!''MovementZone''
	!''Description''		!''Description''
Line 41:		Line 39:
	\|When pathfinding, considers clear ground passable. Assumes it can destroy terrain obstacles and crush infantry.		\|When pathfinding, considers clear ground passable. Assumes it can destroy terrain obstacles and crush infantry.
	\|-		\|-
	!Subterannean		!Subterannean<sup>[[#Notes\|3]]</sup>
	\|When pathfinding, considers clear ground passable. When destination is too far away for surface travel, or there is an obstacle in the way, unit will dig underground. In other cases, when subterranean travel is not possible, or surface travel is quicker, acts like a unit with {{f\|MovementZone\|Crusher}} or {{f\|MovementZone\|Destroyer}}.		\|When pathfinding, considers clear ground passable. When destination is too far away for surface travel, or there is an obstacle in the way, unit will dig underground. In other cases, when subterranean travel is not possible, or surface travel is quicker, acts like a unit with {{f\|MovementZone\|Crusher}} or {{f\|MovementZone\|Destroyer}}.
	This MovementZone is what allows units with Subterranean [[Locomotor]] to dig in if target location and/or origin location can't be dug into courtesy of {{f\|AllowBurrowing\|no\|link}} on the [[TileSets]] and make unit look for the closest cells to dig into and/or out of.		This MovementZone is what allows units with Subterranean [[Locomotor]] to dig in if target location and/or origin location can't be dug into courtesy of {{f\|AllowBurrowing\|no\|link}} on the [[TileSets]] and make unit look for the closest cells to dig into and/or out of.
Line 55:		Line 53:

	=== Notes ===		=== Notes ===
	<sup>1</sup>: To actually crush infantry, it needs to be [[Crusher~~]]=~~yes. Infantry which has [[Crushable~~]]=~~no or [[~~DeployedCrushable~~]]~~=no (YR~~ only, only works when deployed, obviously) set will not be crushable.~~<br />~~		[[SpeedType]] is what actually allows or disallows a unit to move over [[LandTypes\|specific terrain]].
	<sup>2</sup>: In order to actually crush vehicles, it needs to be [[OmniCrusher~~]]=~~yes. Objects which have [[OmniCrushResistant~~]]=~~yes will not be crushable.
			<sup>1</sup>: To actually crush infantry, it needs to be {{f\|Crusher\|yes\|link}}. Infantry which has {{f\|Crushable\|no\|link}} or {{f\|DeployedCrushable\|no\|link}} ([[YR]] only, only works when deployed, obviously) set will not be crushable.

			<sup>2</sup>: In order to actually crush vehicles, it needs to be {{f\|OmniCrusher\|yes\|link}}. Objects which have {{f\|OmniCrushResistant\|yes\|link}} will not be crushable.

			<sup>3</sup>: With a typo, no less. ''Subter'''r'''annean'' will '''not''' work.

	[[Category:INI Flags]]		[[Category:INI Flags]]

en>TAK02 at 17:27, 29 June 2021

2021-06-29T17:27:48Z

← Older revision		Revision as of 19:27, 29 June 2021
Line 42:		Line 42:
	\|-		\|-
	!Subterannean		!Subterannean
	\|When pathfinding, considers clear ground passable. When destination is too far away for surface travel, or there is an obstacle in the way, unit will dig underground~~. Unit cannot dig on pavement~~. In other cases, when subterranean travel is not possible, or surface travel is quicker, acts like a unit with MovementZone=Crusher or MovementZone=Destroyer.		\|When pathfinding, considers clear ground passable. When destination is too far away for surface travel, or there is an obstacle in the way, unit will dig underground. In other cases, when subterranean travel is not possible, or surface travel is quicker, acts like a unit with {{f\|MovementZone\|Crusher}} or {{f\|MovementZone\|Destroyer}}.
			This MovementZone is what allows units with Subterranean [[Locomotor]] to dig in if target location and/or origin location can't be dug into courtesy of {{f\|AllowBurrowing\|no\|link}} on the [[TileSets]] and make unit look for the closest cells to dig into and/or out of.
			If a different {{f\|MovementZone}} is set the unit will only dig if both origin and target locations can be dug into; else it'll drive and only re-consider digging after a complete and absolute stop and ''then'' giving a new order manually. If persuaded to get underground then given a new order it'll try going to new target location, and if it can't dig out of it it'll look for closest exit only after it reaches/gets directly below the target.
	\|-		\|-
	!Water		!Water

en>TAK02: hit that diff button and dbl-chk. Oh who am I kidding. No-one reads or re-chks if Crusher allows subterranean movement after 11 tiles.

2021-05-15T20:01:43Z

hit that diff button and dbl-chk. Oh who am I kidding. No-one reads or re-chks if Crusher allows subterranean movement after 11 tiles.

← Older revision		Revision as of 22:01, 15 May 2021
Line 1:		Line 1:
	{{flag\|name=MovementZone\|files=rules(md).ini\|values=special strings\|default=<tt>Normal</tt>\|types=[[InfantryTypes]], [[VehicleTypes]], [[AircraftTypes]], [[BuildingTypes]] (to the same extent as [[Locomotor]]s do) \|ts=yes\|fs=yes\|ets=yes\|ra2=yes\|yr=yes\|rp=yes}}		{{flag\|name=MovementZone\|files=rules(md).ini\|values=special strings\|default=<tt>Normal</tt>\|types=[[InfantryTypes]], [[VehicleTypes]], [[AircraftTypes]], [[BuildingTypes]] (to the same extent as [[Locomotor]]s do) \|ts=yes\|fs=yes\|ets=yes\|ra2=yes\|yr=yes\|rp=yes}}.
			[[SpeedType]] is what actually allows or disallows a unit to move over [[TileType}}.

	MovementZone says where is the unit allowed to go and helps the [[AI]] pathfinding routines. The possible values it takes are:		MovementZone says where is the unit allowed to go and helps the [[AI]] pathfinding routines. The possible values it takes are:
Line 8:		Line 9:
	!Amphibious		!Amphibious
	\|When pathfinding, the unit will consider both ground and water as passable.		\|When pathfinding, the unit will consider both ground and water as passable.
	This is the only MovementZone that allows amphibious units, like Hover Craft and Robot Tanks or even the TS GDI APC, to dock with {{f\|UnitRepair\|yes\|link}} buildings for repairs, regardless if it's land-based Service Depot or a water-based Naval Yard.		This is the only MovementZone that allows amphibious units, like Hover Craft and Robot Tanks or even the TS GDI APC, to dock with all {{f\|UnitRepair\|yes\|link}} buildings for repairs, regardless if it's land-based Service Depot or a water-based Naval Yard.

			Otherwise the unit will stick with land-based OR water-based, never both.
	\|-		\|-
	!AmphibiousCrusher		!AmphibiousCrusher
Line 18:		Line 21:
	!Crusher		!Crusher
	\|When pathfinding, only clear ground is considered passable. Also assumes that it can crush infantry, but is not armed.<sup>[[#Notes\|1]]</sup>		\|When pathfinding, only clear ground is considered passable. Also assumes that it can crush infantry, but is not armed.<sup>[[#Notes\|1]]</sup>
			Units with Subterranean [[Locomotor]] and Crusher MovementZone will only dig in if there are 11 tiles between unit destination. Those tiles were Clear tiles.
	\|-		\|-
	!CrusherAll		!CrusherAll

en>TAK02: Amphibious is only movementZone that allows units to dock with land and water {{UnitRepair|yes|link}}

2021-04-11T06:22:58Z

Amphibious is only movementZone that allows units to dock with land and water {{UnitRepair|yes|link}}

← Older revision		Revision as of 08:22, 11 April 2021
Line 8:		Line 8:
	!Amphibious		!Amphibious
	\|When pathfinding, the unit will consider both ground and water as passable.		\|When pathfinding, the unit will consider both ground and water as passable.
			This is the only MovementZone that allows amphibious units, like Hover Craft and Robot Tanks or even the TS GDI APC, to dock with {{f\|UnitRepair\|yes\|link}} buildings for repairs, regardless if it's land-based Service Depot or a water-based Naval Yard.
	\|-		\|-
	!AmphibiousCrusher		!AmphibiousCrusher
	\|When pathfinding, the unit will consider both ground and water as ~~passible~~. In addition, it will assume that it is capable of crushing infantry, but is unarmed.<sup>[[#Notes\|1]]</sup>		\|When pathfinding, the unit will consider both ground and water as passable. In addition, it will assume that it is capable of crushing infantry, but is unarmed.<sup>[[#Notes\|1]]</sup>
	\|-		\|-
	!AmphibiousDestroyer		!AmphibiousDestroyer

128.70.176.206 at 01:08, 14 July 2014

2014-07-14T01:08:32Z

← Older revision		Revision as of 03:08, 14 July 2014
Line 41:		Line 41:
	!Water		!Water
	\|When pathfinding, considers only water as passable.		\|When pathfinding, considers only water as passable.
			\|-
			!WaterBeach
			\| ???
			\|-
	\|}		\|}