Movedefs.lua - Revision history

Maddox: Fixed comment about hover class: canHover was removed in 95.0

2022-07-06T19:51:16Z

Fixed comment about hover class: canHover was removed in 95.0

← Older revision		Revision as of 20:51, 6 July 2022
Line 22:		Line 22:
	* <code>Tank</code> - A ground based '''MoveClass'''. Identical to <code>Bot</code> other than interaction with '''TypeMaps'''.		* <code>Tank</code> - A ground based '''MoveClass'''. Identical to <code>Bot</code> other than interaction with '''TypeMaps'''.
	* <code>Ship</code> or <code>Boat</code> - Are synonyms. All ships / boat '''MoveClasses''' must belong to this type to behave as ships.		* <code>Ship</code> or <code>Boat</code> - Are synonyms. All ships / boat '''MoveClasses''' must belong to this type to behave as ships.
	* <code>Hover</code> - All hovercraft '''MoveClasses''' (traverse any depth of water without speed reduction) must belong to this class~~, as well as having {{xtaglink\|Gamedev:UnitDefs\|canHover}} in their [[Gamedev:UnitDefs\|UnitDef]] to behave as hovers~~.		* <code>Hover</code> - All hovercraft '''MoveClasses''' (traverse any depth of water without speed reduction) must belong to this class.

	==MoveClass Tags==		==MoveClass Tags==

2019-08-29T11:12:28Z

flow :/

@@ Line 121: / Line 121: @@
 |default = 30
 |description = How much heat to place on a square if a path goes through it. <code>heat set = max(currentSquareHeat, heatProduced)</code>.
 }}

2019-03-23T01:01:08Z

depthModParams

← Older revision		Revision as of 02:01, 23 March 2019
Line 191:		Line 191:
	\|type = float		\|type = float
	\|default = MAX_FLOAT		\|default = MAX_FLOAT
	\|description = This is the cap on how severe the depth effect can be. For example, lets say that you use a maxScale value of 2. If a unit is near its maximum depth (with a maxScale value of 2), the slowest it will go is half of its maximum speed. In other words, (maxVelocity / maxScale). Therefore, as another example, a value of 4 would cause the unit's maximum speed (near maximum depth) to be 25% of it's maxVelocity.		\|description = This is the cap on how severe the depth effect can be. For example, lets say that you use a maxScale value of 2. If a unit is at the depth where its scale reaches the max (usually near its maximum depth; with a maxScale value of 2), the slowest it will go is half of its maximum speed. In other words, (maxVelocity / maxScale). Therefore, as another example, a value of 4 would cause the unit's maximum speed (near the units maximum depth) to be 25% of it's maxVelocity.
	}}		}}

2019-03-23T00:53:45Z

depthModParams

← Older revision		Revision as of 01:53, 23 March 2019
Line 191:		Line 191:
	\|type = float		\|type = float
	\|default = MAX_FLOAT		\|default = MAX_FLOAT
	\|description = This is the cap on how severe the depth effect can be. ~~That~~ is ~~if the~~ value is 2, the slowest ~~the unit~~ will go ~~because of depth~~ is half-speed. 4 ~~= a quarter~~ speed~~, and so on~~.		\|description = This is the cap on how severe the depth effect can be. For example, lets say that you use a maxScale value of 2. If a unit is near its maximum depth (with a maxScale value of 2), the slowest it will go is half of its maximum speed. In other words, (maxVelocity / maxScale). Therefore, as another example, a value of 4 would cause the unit's maximum speed (near maximum depth) to be 25% of it's maxVelocity.
	}}		}}

2017-12-16T22:17:01Z

MoveClass Tags: 104.0 - incorporate native "raw move" (straight-line path) support

← Older revision		Revision as of 23:17, 16 December 2017
Line 89:		Line 89:
	\|special = {{new\|96.0}}		\|special = {{new\|96.0}}
	\|description = Disable this to improve handling of large (>4 x 4) footprint units (See {{mantis\|4217}}).		\|description = Disable this to improve handling of large (>4 x 4) footprint units (See {{mantis\|4217}}).
			}}

			{{tag
			\|name = allowRawMovement
			\|type = bool
			\|default = false
			\|special = {{new\|104.0}}
			\|description = Enables native "raw move" (straight-line path) support (See also [[Lua_SyncedCtrl\|Spring.SetUnitMoveGoal]] and {{mantis\|4412}}).
	}}		}}

2016-08-02T19:33:06Z

speedModMults: linebreak

← Older revision		Revision as of 20:33, 2 August 2016
Line 211:		Line 211:

	These previously hard-coded variables allow control over how the pathfinder (default only, not [[QTPFS]], see [[Modrules.lua]]) calculates the cost for a '''MoveClass''' for squares containing mobile units, if and only if {{taglink\|avoidMobilesOnPath\|true}}.		These previously hard-coded variables allow control over how the pathfinder (default only, not [[QTPFS]], see [[Modrules.lua]]) calculates the cost for a '''MoveClass''' for squares containing mobile units, if and only if {{taglink\|avoidMobilesOnPath\|true}}.

	{{tag		{{tag
	\|name = mobileBusyMult		\|name = mobileBusyMult

2016-06-12T20:49:42Z

Heat Tags: line break

← Older revision		Revision as of 21:49, 12 June 2016
Line 93:		Line 93:
	=== Heat Tags ===		=== Heat Tags ===
	These tags are used in unit avoidance.		These tags are used in unit avoidance.

	{{tag		{{tag
	\|name = heatMapping		\|name = heatMapping

2015-04-14T17:22:34Z

added: check movedefs

← Older revision		Revision as of 18:22, 14 April 2015
Line 242:		Line 242:

	--kloot, Thu Jul 31, 2008		--kloot, Thu Jul 31, 2008

			==Code to check your movdefs==
			{{forumlink\|topic=24866\|title=A resource to check movedefs}} that game developers have used for years and find it quite useful.

	==Example==		==Example==

2014-10-02T16:57:23Z

Source: data types

← Older revision		Revision as of 17:57, 2 October 2014
Line 9:		Line 9:
	The engine source code which parses the data from this file is viewable here:		The engine source code which parses the data from this file is viewable here:
	* {{sourcelink\|file=rts/Sim/MoveTypes/MoveDefHandler.cpp}}		* {{sourcelink\|file=rts/Sim/MoveTypes/MoveDefHandler.cpp}}

			==Data Types==
			{{DataTypes}}

	==Details==		==Details==

2014-01-03T11:06:02Z

MoveClass Tags: 96.0- MoveDef: add key 'allowTerrainCollisions' for handling units with super-sized footprints (see #4217)

← Older revision		Revision as of 12:06, 3 January 2014
Line 78:		Line 78:
	* Pro: groups moving without a ctrl-order clump much less		* Pro: groups moving without a ctrl-order clump much less
	* Contra: groups moving with a ctrl-order are less organized		* Contra: groups moving with a ctrl-order are less organized
			}}

			{{tag
			\|name = allowTerrainCollisions
			\|type = bool
			\|default = true
			\|special = {{new\|96.0}}
			\|description = Disable this to improve handling of large (>4 x 4) footprint units (See {{mantis\|4217}}).
	}}		}}