JumpjetAccel - Revision history

ATHSE at 16:35, 11 April 2025

2025-04-11T16:35:53Z

← Older revision		Revision as of 18:35, 11 April 2025
Line 11:		Line 11:
	Defines the acceleration and deceleration of this unit when flying using the Jumpjet locomotor. The deceleration is calculated by {{f\|JumpjetAccel}} {{tt\|* 1.5}}.		Defines the acceleration and deceleration of this unit when flying using the Jumpjet locomotor. The deceleration is calculated by {{f\|JumpjetAccel}} {{tt\|* 1.5}}.

	This tag should be used with caution, as it can render Landable=yes units unable to actually land, due to the deceleration math never reaching exactly zero, and the unit will remain hovering at full (animation) speed without ever transitioning to idle speed.		This tag should be used with caution, as it can render {{f\|Landable\|yes\|link}} units unable to actually land, due to the deceleration math never reaching exactly zero, and the unit will remain hovering at full (animation) speed without ever transitioning to idle speed.

	==See also==		==See also==
	* {{f\|Jumpjet~~\|link}}~~		[[Jumpjet]]

			[[JumpjetControls]]

MarkJFox: 7 revisions imported

2025-03-31T19:51:26Z

7 revisions imported

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

en>ATHSE at 14:03, 9 April 2023

2023-04-09T14:03:59Z

← Older revision		Revision as of 16:03, 9 April 2023
Line 9:		Line 9:
	}}		}}

	Defines the acceleration and deceleration of this unit when flying using the Jumpjet locomotor.		Defines the acceleration and deceleration of this unit when flying using the Jumpjet locomotor. The deceleration is calculated by {{f\|JumpjetAccel}} {{tt\|* 1.5}}.

	~~The~~ deceleration ~~is calculated by {{f\|JumpjetAccel}} {{tt\|* 1.5}}~~.		This tag should be used with caution, as it can render Landable=yes units unable to actually land, due to the deceleration math never reaching exactly zero, and the unit will remain hovering at full (animation) speed without ever transitioning to idle speed.

	==See also==		==See also==
	* {{f\|Jumpjet\|link}}		* {{f\|Jumpjet\|link}}

en>AlexB at 17:24, 4 December 2017

2017-12-04T17:24:48Z

@@ Line 1: / Line 1: @@
-This flag is, in fact, NOT parsed. {{f|JumpJetAccel|link}} is parsed instead.
+{{Flag
-Typing JumpjetAccel instead will make the JumpJet unit never land in a similar fashion to {{f|BalloonHover|link}}. As a result, {{f|AG|link}}-only weapons won't target the unit. Only those with {{f|AA|link}}=yes.
+Defines the acceleration and deceleration of this unit when flying using the Jumpjet locomotor.
-In theory, mis-casing it can be used as a 'fix' for the problem with BallonHover-ers always willing to occupy the same cell as the target.
+The deceleration is calculated by {{f|JumpjetAccel}} {{tt|* 1.5}}.

en>TAK02 at 13:02, 22 July 2017

2017-07-22T13:02:46Z

← Older revision		Revision as of 15:02, 22 July 2017
Line 2:		Line 2:

	Typing JumpjetAccel instead will make the JumpJet unit never land in a similar fashion to {{f\|BalloonHover\|link}}. As a result, {{f\|AG\|link}}-only weapons won't target the unit. Only those with {{f\|AA\|link}}=yes.		Typing JumpjetAccel instead will make the JumpJet unit never land in a similar fashion to {{f\|BalloonHover\|link}}. As a result, {{f\|AG\|link}}-only weapons won't target the unit. Only those with {{f\|AA\|link}}=yes.
			The unit will attempt to land, but never do so, but hovers in the air a short distance away from the ground.

	In theory, mis-casing it can be used as a 'fix' for the problem with BallonHover-ers always willing to occupy the same cell as the target.		In theory, mis-casing it can be used as a 'fix' for the problem with BallonHover-ers always willing to occupy the same cell as the target.

en>TAK02: Put up what happens when mis-casing JumpJetAccel

2017-07-22T12:58:10Z

Put up what happens when mis-casing JumpJetAccel

← Older revision		Revision as of 14:58, 22 July 2017
Line 1:		Line 1:
	This flag is, in fact, NOT parsed. {{f\|JumpJetAccel\|link}} is parsed instead		This flag is, in fact, NOT parsed. {{f\|JumpJetAccel\|link}} is parsed instead.

			Typing JumpjetAccel instead will make the JumpJet unit never land in a similar fashion to {{f\|BalloonHover\|link}}. As a result, {{f\|AG\|link}}-only weapons won't target the unit. Only those with {{f\|AA\|link}}=yes.

			In theory, mis-casing it can be used as a 'fix' for the problem with BallonHover-ers always willing to occupy the same cell as the target.

en>TAK02: linked

2017-02-17T14:42:29Z

linked

← Older revision		Revision as of 16:42, 17 February 2017
Line 1:		Line 1:
	This flag is, in fact, NOT parsed. JumpJetAccel is parsed instead		This flag is, in fact, NOT parsed. {{f\|JumpJetAccel\|link}} is parsed instead

en>TAK02: JumpjetAccel is NOT read. It's written with TWO big 'J's

2017-02-17T14:29:46Z

JumpjetAccel is NOT read. It's written with TWO big 'J's

← Older revision		Revision as of 16:29, 17 February 2017
Line 1:		Line 1:
	~~{{DeeZireInclusion}}<br />~~		This flag is, in fact, NOT parsed. JumpJetAccel is parsed instead
	~~The acceleration of this unit which has JumpJet=yes assigned and acts as an over-ride to the Acceleration= statement~~ in ~~the JumpjetControls section~~. ~~NOTE: this tag~~ is ~~a spelling mistake in RULES.INI - there should not be a second capital 'j'.~~

en>DCoder at 15:52, 5 May 2006

2006-05-05T15:52:50Z

New page

{{DeeZireInclusion}}<br />
The acceleration of this unit which has JumpJet=yes assigned and acts as an over-ride to the Acceleration= statement in the JumpjetControls section. NOTE: this tag is a spelling mistake in RULES.INI - there should not be a second capital 'j'.