Specialist (LW2) - Revision history

Solymr at 19:04, 5 September 2020

2020-09-05T19:04:56Z

← Older revision		Revision as of 19:04, 5 September 2020
Line 15:		Line 15:
	===Weapons===		===Weapons===

	'''Primary''': [[Weapons_(LW2)#~~Assault_Rifle~~\|Rifles]], [[Weapons_(LW2)#Submachine_Guns\|SMGs]], [[Weapons_(LW2)#~~Shotgun~~\|Shotguns]].		'''Primary''': [[Weapons_(LW2)#Assault_Rifles\|Rifles]], [[Weapons_(LW2)#Submachine_Guns\|SMGs]], [[Weapons_(LW2)#Shotguns\|Shotguns]].

	'''Secondary''': [[Weapons_(LW2)#~~GREMLIN~~\|GREMLIN]]		'''Secondary''': [[Weapons_(LW2)#GREMLINs\|GREMLIN]]

	As with vanilla, Specialists use GREMLINs as secondaries, allowing them to perform many actions at range. Better GREMLINs improve their abilities as well as their Hacking stat.		As with vanilla, Specialists use GREMLINs as secondaries, allowing them to perform many actions at range. Better GREMLINs improve their abilities as well as their Hacking stat.

Solymr at 11:52, 20 August 2020

2020-08-20T11:52:21Z

← Older revision		Revision as of 11:52, 20 August 2020
Line 1:		Line 1:
	{{Toc_(LW2)}}'''Operating some of our most advanced equipment, Specialists deploy robotic drones on the battlefield that can be outfitted for combat or field medic duty.'''		{{Toc_(LW2)\|0}}[[File:XCOM2 class specialist.png\|center\|frameless\|96px\|Specialist]]<div style="text-align: center;">'''''Operating some of our most advanced equipment, Specialists deploy robotic drones on the battlefield that can be outfitted for combat or field medic duty.'''''</div>

	~~Primary: Rifle(default), SMG or Shotgun; Secondary: Gremlin~~		==Class Overview==

	Specialists in Long War 2 are largely similar to XCOM 2's Specialist class, with several exceptions. Haywire Protocol is available for all Specialists from the start, allowing you to build out medical specialists while still putting their Hack stat to use. Combat Hackers gain more options and failsafes to allow them to hack and control foes while managing the consequences of success and failure in XCOM's favor.		Specialists in Long War 2 are largely similar to XCOM 2's Specialist class, with several exceptions. Haywire Protocol is available for all Specialists from the start, allowing you to build out medical specialists while still putting their Hack stat to use. Combat Hackers gain more options and failsafes to allow them to hack and control foes while managing the consequences of success and failure in XCOM's favor.
Line 13:		Line 13:
	Lastly, as with XCOM 2, including one specialist of any rank in a squad is vital if the mission objective entails hacking a container, door, or other electronic node, allowing you to complete your mission objective from sight range rather than melee range, and even if the rest of your squad is bogged down in a firefight.		Lastly, as with XCOM 2, including one specialist of any rank in a squad is vital if the mission objective entails hacking a container, door, or other electronic node, allowing you to complete your mission objective from sight range rather than melee range, and even if the rest of your squad is bogged down in a firefight.

	== ~~Abilities~~ (~~As of~~ LW2 ~~Version 1~~.3) ==		===Weapons===

			'''Primary''': [[Weapons_(LW2)#Assault_Rifle\|Rifles]], [[Weapons_(LW2)#Submachine_Guns\|SMGs]], [[Weapons_(LW2)#Shotgun\|Shotguns]].

			'''Secondary''': [[Weapons_(LW2)#GREMLIN\|GREMLIN]]

			As with vanilla, Specialists use GREMLINs as secondaries, allowing them to perform many actions at range. Better GREMLINs improve their abilities as well as their Hacking stat.

			== Abilities ==
	{{Class Tree (LW2)		{{Class Tree (LW2)
	\|Squaddie1={{Aid Protocol (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|Squaddie1={{Aid Protocol (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
Line 42:		Line 50:
	\|MSgt3={{Capacitor Discharge (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|MSgt3={{Capacitor Discharge (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	}}		}}

			* Once you have researched plasma grenades, Airdrop will begin dropping them instead of frag grenades.
			* Haywire Protocol/Full Override:
			** A control-hacked turret has its Action Points available starting on the current turn.
			** A control-hacked MEC (that is not a turret) will have its Action Points available starting on the following turn.

	== Stat Progression ==		== Stat Progression ==
Line 95:		Line 108:
	}}		}}
	*This class also gains 1 point of strength, though it's only used for alien abilities.		*This class also gains 1 point of strength, though it's only used for alien abilities.
	~~== Perk Details ==~~
	* Once you have researched plasma grenades, airdrop will begin dropping them instead of frag grenades.
	* Haywire Protocol/Full Override:
	** A control-hacked turret has its Action Points available starting on the current turn.
	** A control-hacked MEC (that is not a turret) will have its Action Points available starting on the following turn.

	==See Also==		==See Also==

Solymr at 18:58, 19 August 2020

2020-08-19T18:58:26Z

← Older revision		Revision as of 18:58, 19 August 2020
Line 1:		Line 1:
	'''Operating some of our most advanced equipment, Specialists deploy robotic drones on the battlefield that can be outfitted for combat or field medic duty.'''		{{Toc_(LW2)}}'''Operating some of our most advanced equipment, Specialists deploy robotic drones on the battlefield that can be outfitted for combat or field medic duty.'''

	Primary: Rifle(default), SMG or Shotgun; Secondary: Gremlin		Primary: Rifle(default), SMG or Shotgun; Secondary: Gremlin
Line 56:		Line 56:
	\| i_mobility1 = 0		\| i_mobility1 = 0
	\| i_dodge1 = 0		\| i_dodge1 = 0
	\| i_hacking1 = 5		\| i_hacking1 = 10
	\| i_health2 = 0		\| i_health2 = 0
	\| i_offense2 = 2		\| i_offense2 = 2

Solymr: Searching the code for eStat_Strength reveals the only purpose as of now in both vanilla and LW2 is for stun lancer's effect check

2020-08-19T14:26:24Z

Searching the code for eStat_Strength reveals the only purpose as of now in both vanilla and LW2 is for stun lancer's effect check

← Older revision		Revision as of 14:26, 19 August 2020
Line 94:		Line 94:
	\| i_hacking7 = 5		\| i_hacking7 = 5
	}}		}}
			*This class also gains 1 point of strength, though it's only used for alien abilities.
	This class also gains 1 point of strength, though it's ~~not clear what that does~~.

	== Perk Details ==		== Perk Details ==
	* Once you have researched plasma grenades, airdrop will begin dropping them instead of frag grenades.		* Once you have researched plasma grenades, airdrop will begin dropping them instead of frag grenades.

Lieronet: Removed mention of a bug in Full Override. As of 1.5 you can keep overridden MECs for the resistance on a mission where you don't keep corpses. Saw it happen on Jorbs' stream less in June.

2020-07-09T19:49:00Z

Removed mention of a bug in Full Override. As of 1.5 you can keep overridden MECs for the resistance on a mission where you don't keep corpses. Saw it happen on Jorbs' stream less in June.

← Older revision		Revision as of 19:49, 9 July 2020
Line 98:		Line 98:

	== Perk Details ==		== Perk Details ==
	* Due to a current bug, in order to keep a mec from a Full Override hack, the mission must be one where you can keep corpses. Verify?
	* Once you have researched plasma grenades, airdrop will begin dropping them instead of frag grenades.		* Once you have researched plasma grenades, airdrop will begin dropping them instead of frag grenades.
	* Haywire Protocol/Full Override:		* Haywire Protocol/Full Override:

Faket15 at 22:39, 4 June 2017

2017-06-04T22:39:31Z

← Older revision		Revision as of 22:39, 4 June 2017
Line 15:		Line 15:
	== Abilities (As of LW2 Version 1.3) ==		== Abilities (As of LW2 Version 1.3) ==
	{{Class Tree (LW2)		{{Class Tree (LW2)
	\|Squaddie1={{Aid Protocol (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 0 \| b_table = 1 }}		\|Squaddie1={{Aid Protocol (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|Squaddie2={{Haywire Protocol (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 0 \| b_table = 1 }}		\|Squaddie2={{Haywire Protocol (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|Squaddie3={{Hack (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|Squaddie3={{Hack (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|Subclass1=Medic		\|Subclass1=Medic

Faket15 at 01:25, 16 May 2017

2017-05-16T01:25:07Z

Exo2000: /* Perk Details */ Trojan bug was fixed

2017-05-15T14:42:58Z

Perk Details: Trojan bug was fixed

← Older revision		Revision as of 14:42, 15 May 2017
Line 103:		Line 103:
	** A control-hacked turret has its Action Points available starting on the current turn.		** A control-hacked turret has its Action Points available starting on the current turn.
	** A control-hacked MEC (that is not a turret) will have its Action Points available starting on the following turn.		** A control-hacked MEC (that is not a turret) will have its Action Points available starting on the following turn.
	* Trojan does not apply to hacks via Squadsight. (this bug [http://www.pavonisinteractive.com/phpBB3/viewtopic.php?f=21&t=24610#p36421 will probably be fixed with 1.3])

	==See Also==		==See Also==

Jafar Ironclad: Added version note to Abilities subheading. Remove when tree updated to 1.3

2017-04-11T11:00:51Z

Added version note to Abilities subheading. Remove when tree updated to 1.3

← Older revision		Revision as of 11:00, 11 April 2017
Line 13:		Line 13:
	Lastly, as with XCOM 2, including one specialist of any rank in a squad is vital if the mission objective entails hacking a container, door, or other electronic node, allowing you to complete your mission objective from sight range rather than melee range, and even if the rest of your squad is bogged down in a firefight.		Lastly, as with XCOM 2, including one specialist of any rank in a squad is vital if the mission objective entails hacking a container, door, or other electronic node, allowing you to complete your mission objective from sight range rather than melee range, and even if the rest of your squad is bogged down in a firefight.

	== Abilities ==		== Abilities (As of LW2 Version 1.2) ==
	{{Class Tree (LW2)		{{Class Tree (LW2)
	\|Squaddie1={{Aid Protocol (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 0 \| b_table = 1 }}		\|Squaddie1={{Aid Protocol (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 0 \| b_table = 1 }}

Falconeye: /* See Also */

2017-04-08T23:13:05Z

← Older revision		Revision as of 23:13, 8 April 2017
Line 109:		Line 109:
	{{XCOM_Units_Navbar_(LW2)}}		{{XCOM_Units_Navbar_(LW2)}}

	~~[[Category: Long War 2]]~~		[[Category:Soldiers (Long War 2)]]
	[[Category: Soldiers ~~(Long War 2)]]~~
	~~[[Category: Classes~~ (Long War 2)]]

← Older revision		Revision as of 01:25, 16 May 2017
Line 13:		Line 13:
	Lastly, as with XCOM 2, including one specialist of any rank in a squad is vital if the mission objective entails hacking a container, door, or other electronic node, allowing you to complete your mission objective from sight range rather than melee range, and even if the rest of your squad is bogged down in a firefight.		Lastly, as with XCOM 2, including one specialist of any rank in a squad is vital if the mission objective entails hacking a container, door, or other electronic node, allowing you to complete your mission objective from sight range rather than melee range, and even if the rest of your squad is bogged down in a firefight.

	== Abilities (As of LW2 Version 1.2) ==		== Abilities (As of LW2 Version 1.3) ==
	{{Class Tree (LW2)		{{Class Tree (LW2)
	\|Squaddie1={{Aid Protocol (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 0 \| b_table = 1 }}		\|Squaddie1={{Aid Protocol (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 0 \| b_table = 1 }}
Line 20:		Line 20:
	\|Subclass1=Medic		\|Subclass1=Medic
	\|Subclass2=Hacker		\|Subclass2=Hacker
	\|LCorporal1={{~~Medical~~ Protocol (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|LCorporal1={{Revival Protocol (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|LCorporal2={{~~Cool Under Pressure~~ (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|LCorporal2={{Sentinel (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|LCorporal3={{Combat Protocol (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|LCorporal3={{Combat Protocol (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|Corporal1={{~~Revival Protocol~~ (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|Corporal1={{Field Surgeon (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|Corporal2={{Covering Fire (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|Corporal2={{Covering Fire (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|Corporal3={{Interference (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|Corporal3={{Interference (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|Sergeant1={{~~Field Medic~~ (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|Sergeant1={{Medical Protocol (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|Sergeant2={{~~Suppression~~ (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|Sergeant2={{Scanning Protocol (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|Sergeant3={{~~Airdrop~~ (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|Sergeant3={{Trojan (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|StaffSgt1={{Field ~~Surgeon~~ (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|StaffSgt1={{Field Medic (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|StaffSgt2={{Ever Vigilant (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|StaffSgt2={{Ever Vigilant (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|StaffSgt3={{~~Failsafe~~ (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|StaffSgt3={{Airdrop (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|TechSgt1={{Savior (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|TechSgt1={{Savior (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|TechSgt2={{~~Sentinel~~ (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|TechSgt2={{Cool Under Pressure (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|TechSgt3={{~~Trojan~~ (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|TechSgt3={{Failsafe (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|GunSgt1={{~~Scanning~~ Protocol (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|GunSgt1={{Rescue Protocol (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|GunSgt2={{~~Kill Zone~~ (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|GunSgt2={{Threat Assessment (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|GunSgt3={{~~Threat Assessment~~ (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|GunSgt3={{Full Override (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|MSgt1={{Restoration (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|MSgt1={{Restoration (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|MSgt2={{~~Full Override~~ (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|MSgt2={{Kill Zone (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	\|MSgt3={{Capacitor Discharge (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}		\|MSgt3={{Capacitor Discharge (LW2) \| b_name = 1 \| b_descr = 1 \| b_info = 1 \| b_table = 1 }}
	}}		}}