WeaponX - Revision history

Rain-Islet: [bot] Batch update {{Bugs}} templates.

2025-07-02T16:05:12Z

[bot] Batch update {{Bugs}} templates.

← Older revision		Revision as of 18:05, 2 July 2025
Line 26:		Line 26:
	Every two {{tt\|WeaponX}} will form a group to handle the AG and AA tasks in each phase of Gattling. For specific operational details, please refer to [[IsGattling]].		Every two {{tt\|WeaponX}} will form a group to handle the AG and AA tasks in each phase of Gattling. For specific operational details, please refer to [[IsGattling]].

	{{Bugs}}		=={{Bugs}}==
	In the original games, there can be only one IFV unit, hardcoded to the unit named [FV]. Otherwise, the Turret will not be drawn.		In the original games, there can be only one IFV unit, hardcoded to the unit named [FV]. Otherwise, the Turret will not be drawn.
	*Ares fixes this, and allows any vehicle to function as an IFV, with more turrets: https://ares-developers.github.io/Ares-docs/new/gunner.html		*Ares fixes this, and allows any vehicle to function as an IFV, with more turrets: https://ares-developers.github.io/Ares-docs/new/gunner.html

ATHSE at 10:24, 8 April 2025

2025-04-08T10:24:07Z

← Older revision		Revision as of 12:24, 8 April 2025
Line 29:		Line 29:
	In the original games, there can be only one IFV unit, hardcoded to the unit named [FV]. Otherwise, the Turret will not be drawn.		In the original games, there can be only one IFV unit, hardcoded to the unit named [FV]. Otherwise, the Turret will not be drawn.
	*Ares fixes this, and allows any vehicle to function as an IFV, with more turrets: https://ares-developers.github.io/Ares-docs/new/gunner.html		*Ares fixes this, and allows any vehicle to function as an IFV, with more turrets: https://ares-developers.github.io/Ares-docs/new/gunner.html

			==See Also==
			[[IFV Weapon System]]

DeathFish: WeaponN -> WeaponX, Gattling guided text

2025-04-08T03:43:40Z

WeaponN -> WeaponX, Gattling guided text

← Older revision		Revision as of 05:43, 8 April 2025
Line 10:		Line 10:

	==IFV Logic==		==IFV Logic==
	Weapon number 'N' (ie. Weapon1=someweapon) specifies the weapon available on the named turret with the value of 'N', for example ShockTurretWeapon. One possibly confusing aspect is that the turret used, as defined by the named turret index doesn't have to match the weapon number, many of the IFV weapons actually use the same turret art.		Weapon number 'X' (ie. Weapon1=someweapon) specifies the weapon available on the named turret with the value of 'X', for example ShockTurretWeapon. One possibly confusing aspect is that the turret used, as defined by the named turret index doesn't have to match the weapon number, many of the IFV weapons actually use the same turret art.

	There are 13 IFV turrets in the original RA2, expanded to 17 in YR, defined by [[TurretCount]], each with its own weapon. In RA2 this means there are Weapon1 through Weapon13 tags on the IFV, along with [[EliteWeaponX\|EliteWeapon]] versions. There is also a special case for NormalTurretWeapon which applies without a passenger too.		There are 13 IFV turrets in the original RA2, expanded to 17 in YR, defined by [[TurretCount]], each with its own weapon. In RA2 this means there are Weapon1 through Weapon13 tags on the IFV, along with [[EliteWeaponX\|EliteWeapon]] versions. There is also a special case for NormalTurretWeapon which applies without a passenger too.
Line 19:		Line 19:

	==Charge Turret Logic==		==Charge Turret Logic==
	This use of ~~WeaponN~~ is decoupled from the turret changing, and instead only uses 1 weapon for multiple turrets, and as such WeaponCount will always be 1, while TurretCount will always be higher.		This use of {{tt\|WeaponX}} is decoupled from the turret changing, and instead only uses 1 weapon for multiple turrets, and as such WeaponCount will always be 1, while TurretCount will always be higher.

	Charge turret logic also works backwards, and should be considered more like a recoil or cooldown animation, with the turret changing sequence happening after the weapon is fired. In the case of the Prism Tank, the reflective flap is closed until fired, then fully opened immediately after, slowly closing thereafter, rather than getting into a firing state just before firing.		Charge turret logic also works backwards, and should be considered more like a recoil or cooldown animation, with the turret changing sequence happening after the weapon is fired. In the case of the Prism Tank, the reflective flap is closed until fired, then fully opened immediately after, slowly closing thereafter, rather than getting into a firing state just before firing.

	==Gattling Logic==		==Gattling Logic==
	~~See:~~ [[IsGattling]]		Every two {{tt\|WeaponX}} will form a group to handle the AG and AA tasks in each phase of Gattling. For specific operational details, please refer to [[IsGattling]].

	{{Bugs}}		{{Bugs}}
	In the original games, there can be only one IFV unit, hardcoded to the unit named FV.		In the original games, there can be only one IFV unit, hardcoded to the unit named [FV]. Otherwise, the Turret will not be drawn.
	*Ares fixes this, and allows any vehicle to function as an IFV, with more turrets: https://ares-developers.github.io/Ares-docs/new/gunner.html		*Ares fixes this, and allows any vehicle to function as an IFV, with more turrets: https://ares-developers.github.io/Ares-docs/new/gunner.html

ATHSE at 02:54, 8 April 2025

2025-04-08T02:54:06Z

← Older revision		Revision as of 04:54, 8 April 2025
Line 21:		Line 21:
	This use of WeaponN is decoupled from the turret changing, and instead only uses 1 weapon for multiple turrets, and as such WeaponCount will always be 1, while TurretCount will always be higher.		This use of WeaponN is decoupled from the turret changing, and instead only uses 1 weapon for multiple turrets, and as such WeaponCount will always be 1, while TurretCount will always be higher.

	Charge turret logic also works backwards, and should be considered more like a 'cooldown~~' turret~~, with the turret changing sequence happening after the weapon is fired. In the case of the Prism Tank, the reflective flap is closed until fired, then fully opened immediately after, slowly closing thereafter, rather than getting into a firing state just before firing.		Charge turret logic also works backwards, and should be considered more like a recoil or cooldown animation, with the turret changing sequence happening after the weapon is fired. In the case of the Prism Tank, the reflective flap is closed until fired, then fully opened immediately after, slowly closing thereafter, rather than getting into a firing state just before firing.

	The charge turret logic can also be used more simply to mimic loaded and unloaded states, similar to [[NoSpawnAlt]] on {{f\|Spawner\|yes\|link}} vehicles, with turret 1 art showing a loaded state, and turret 2 showing unloaded. The main behavioural difference, aside from the projectile not being an independent spawned [[AircraftTypes\|aircraft]], is that because it is a turret, it can face the target without the whole unit having to turn.

	==Gattling Logic==		==Gattling Logic==

ATHSE: link

2025-04-06T03:34:20Z

link

← Older revision		Revision as of 05:34, 6 April 2025
Line 7:		Line 7:
	\|yr=yes		\|yr=yes
	}}		}}
	This tag forms part of the turret changing logic {{ra2}}, either as part of {{f\|IsChargeTurret\|yes\|link}} as in the case of the Prism Tank, or as part of the IFV passenger-based turret logic using {{f\|Gunner\|yes\|link}}. It is also used by the Gattling tank weapon spooling system added in YR.		This tag forms part of the turret changing logic {{ra2}}, either as part of {{f\|IsChargeTurret\|yes\|link}} as in the case of the Prism Tank, or as part of the IFV passenger-based turret logic using {{f\|Gunner\|yes\|link}}. It is also used by the Gattling tank weapon spooling system added in {{yr}}.

	==IFV Logic==		==IFV Logic==

ATHSE: typo

2025-04-06T03:31:28Z

typo

← Older revision		Revision as of 05:31, 6 April 2025
Line 23:		Line 23:
	Charge turret logic also works backwards, and should be considered more like a 'cooldown' turret, with the turret changing sequence happening after the weapon is fired. In the case of the Prism Tank, the reflective flap is closed until fired, then fully opened immediately after, slowly closing thereafter, rather than getting into a firing state just before firing.		Charge turret logic also works backwards, and should be considered more like a 'cooldown' turret, with the turret changing sequence happening after the weapon is fired. In the case of the Prism Tank, the reflective flap is closed until fired, then fully opened immediately after, slowly closing thereafter, rather than getting into a firing state just before firing.

	The charge turret logic can also be used more simply to mimic loaded and unloaded ~~stated~~, similar to [[NoSpawnAlt]] on {{f\|Spawner\|yes\|link}} vehicles, with turret 1 art showing a loaded state, and turret 2 showing unloaded. The main behavioural difference, aside from the projectile not being an independent spawned [[AircraftTypes\|aircraft]], is that because it is a turret, it can face the target without the whole unit having to turn.		The charge turret logic can also be used more simply to mimic loaded and unloaded states, similar to [[NoSpawnAlt]] on {{f\|Spawner\|yes\|link}} vehicles, with turret 1 art showing a loaded state, and turret 2 showing unloaded. The main behavioural difference, aside from the projectile not being an independent spawned [[AircraftTypes\|aircraft]], is that because it is a turret, it can face the target without the whole unit having to turn.

	==Gattling Logic==		==Gattling Logic==

ATHSE: link fix

2025-04-06T02:37:25Z

link fix

← Older revision		Revision as of 04:37, 6 April 2025
Line 16:		Line 16:
	Infantry meant to board the IFV must have [[IFVMode]] set to to select the weapon the IFV will have when loaded. Importantly, the IFVMode value applies to the IFV turret weapon, not the turret index, so while the Initiate has IFVMode=13, matching InitiateTurretWeapon=13, it does not match InitiateTurretIndex=3.		Infantry meant to board the IFV must have [[IFVMode]] set to to select the weapon the IFV will have when loaded. Importantly, the IFVMode value applies to the IFV turret weapon, not the turret index, so while the Initiate has IFVMode=13, matching InitiateTurretWeapon=13, it does not match InitiateTurretIndex=3.

	{{HorizontalBar\|[[Image:Cc_documentinfo.png‎\|24px]] In YR there is a similar but unrelated [[OpenTopped]] logic, where infantry specify their [[~~OpenToppedWeapon~~]] instead.}}		{{HorizontalBar\|[[Image:Cc_documentinfo.png‎\|24px]] In YR there is a similar but unrelated [[OpenTopped]] logic, where infantry specify their [[OpenTransportWeapon]] instead.}}

	==Charge Turret Logic==		==Charge Turret Logic==

ATHSE at 02:33, 6 April 2025

2025-04-06T02:33:03Z

← Older revision		Revision as of 04:33, 6 April 2025
Line 12:		Line 12:
	Weapon number 'N' (ie. Weapon1=someweapon) specifies the weapon available on the named turret with the value of 'N', for example ShockTurretWeapon. One possibly confusing aspect is that the turret used, as defined by the named turret index doesn't have to match the weapon number, many of the IFV weapons actually use the same turret art.		Weapon number 'N' (ie. Weapon1=someweapon) specifies the weapon available on the named turret with the value of 'N', for example ShockTurretWeapon. One possibly confusing aspect is that the turret used, as defined by the named turret index doesn't have to match the weapon number, many of the IFV weapons actually use the same turret art.

	There are 13 IFV turrets in the original RA2, expanded to 17 in YR, defined by [[TurretCount]], ~~but not necessarily matching the [[WeaponCount]] as there can be more weapons than turrets~~. In RA2 this means there are Weapon1 through Weapon13 tags on the IFV, along with [[EliteWeaponX\|EliteWeapon]] versions. There is also a special case for NormalTurretWeapon which applies without a passenger too.		There are 13 IFV turrets in the original RA2, expanded to 17 in YR, defined by [[TurretCount]], each with its own weapon. In RA2 this means there are Weapon1 through Weapon13 tags on the IFV, along with [[EliteWeaponX\|EliteWeapon]] versions. There is also a special case for NormalTurretWeapon which applies without a passenger too.

	Infantry meant to board the IFV must have [[IFVMode]] set to to select the weapon the IFV will have when loaded. Importantly, the IFVMode value applies to the IFV turret weapon, not the turret index, so while the Initiate has IFVMode=13, matching InitiateTurretWeapon=13, it does not match InitiateTurretIndex=3.		Infantry meant to board the IFV must have [[IFVMode]] set to to select the weapon the IFV will have when loaded. Importantly, the IFVMode value applies to the IFV turret weapon, not the turret index, so while the Initiate has IFVMode=13, matching InitiateTurretWeapon=13, it does not match InitiateTurretIndex=3.

ATHSE at 02:30, 6 April 2025

2025-04-06T02:30:32Z

← Older revision		Revision as of 04:30, 6 April 2025
Line 1:		Line 1:
	{{Flag		{{Flag
	\|~~name~~={{~~PAGENAME~~}} ~~(substitute X with an integer)~~		\|files={{Categ\|ini=rules}}
	\|~~files~~={{~~Categ~~\|~~Rules(md).ini~~}}		\|values={{Values\|uint}}
	~~\|values=strings (names of [[Weapon]]s)~~		\|default=0
	\|default=~~none~~		\|types={{Categ\|VehicleTypes}}
	\|types={{Categ\|VehicleTypes~~}}, {{Categ\|BuildingTypes~~}}
	\|ra2=yes		\|ra2=yes
	\|yr=yes		\|yr=yes
	~~\|rp=yes~~
	}}		}}
	~~Specifies a special case weapon for this object. Special cases are those which don't use~~ the ~~traditional Primary/Secondary weapon systems, for example,~~ turret~~-changers (~~{{~~f\|Gunner\|yes\|link~~}}), ~~charge turrets (~~{{f\|IsChargeTurret\|yes\|link}}), or ~~gattling~~ logic ({{f\|~~IsGattling~~\|yes\|link}}).		This tag forms part of the turret changing logic {{ra2}}, either as part of {{f\|IsChargeTurret\|yes\|link}} as in the case of the Prism Tank, or as part of the IFV passenger-based turret logic using {{f\|Gunner\|yes\|link}}. It is also used by the Gattling tank weapon spooling system added in YR.

	==~~Note~~==		==IFV Logic==
	*Since [[~~WeaponX~~]] ~~doesn't~~ have a ~~fixed limit~~, ~~most players~~ will ~~probably only see~~ [[~~Weapon17~~]], ~~so I added~~ the ~~tag.~~ [[~~Weapon18~~]],[[~~Weapon19~~]] to ~~let other players know~~.		Weapon number 'N' (ie. Weapon1=someweapon) specifies the weapon available on the named turret with the value of 'N', for example ShockTurretWeapon. One possibly confusing aspect is that the turret used, as defined by the named turret index doesn't have to match the weapon number, many of the IFV weapons actually use the same turret art.

			There are 13 IFV turrets in the original RA2, expanded to 17 in YR, defined by [[TurretCount]], but not necessarily matching the [[WeaponCount]] as there can be more weapons than turrets. In RA2 this means there are Weapon1 through Weapon13 tags on the IFV, along with [[EliteWeaponX\|EliteWeapon]] versions. There is also a special case for NormalTurretWeapon which applies without a passenger too.

			Infantry meant to board the IFV must have [[IFVMode]] set to to select the weapon the IFV will have when loaded. Importantly, the IFVMode value applies to the IFV turret weapon, not the turret index, so while the Initiate has IFVMode=13, matching InitiateTurretWeapon=13, it does not match InitiateTurretIndex=3.

			{{HorizontalBar\|[[Image:Cc_documentinfo.png‎\|24px]] In YR there is a similar but unrelated [[OpenTopped]] logic, where infantry specify their [[OpenToppedWeapon]] instead.}}

			==Charge Turret Logic==
			This use of WeaponN is decoupled from the turret changing, and instead only uses 1 weapon for multiple turrets, and as such WeaponCount will always be 1, while TurretCount will always be higher.

			Charge turret logic also works backwards, and should be considered more like a 'cooldown' turret, with the turret changing sequence happening after the weapon is fired. In the case of the Prism Tank, the reflective flap is closed until fired, then fully opened immediately after, slowly closing thereafter, rather than getting into a firing state just before firing.

			The charge turret logic can also be used more simply to mimic loaded and unloaded stated, similar to [[NoSpawnAlt]] on {{f\|Spawner\|yes\|link}} vehicles, with turret 1 art showing a loaded state, and turret 2 showing unloaded. The main behavioural difference, aside from the projectile not being an independent spawned [[AircraftTypes\|aircraft]], is that because it is a turret, it can face the target without the whole unit having to turn.

			==Gattling Logic==
			See: [[IsGattling]]

			{{Bugs}}
			In the original games, there can be only one IFV unit, hardcoded to the unit named FV.
			*Ares fixes this, and allows any vehicle to function as an IFV, with more turrets: https://ares-developers.github.io/Ares-docs/new/gunner.html

MarkJFox: 6 revisions imported

2025-03-31T20:11:45Z

6 revisions imported

← Older revision	Revision as of 22:11, 31 March 2025
(No difference)