Mask of a Fanatic - Revision history

Mobius: Same as before.

2022-09-27T07:11:44Z

Same as before.

Mobius: Same as before

2020-12-30T10:55:59Z

Same as before

Nyctaeus at 23:36, 4 November 2020

2020-11-04T23:36:38Z

Mobius: Background data

2020-10-25T17:55:23Z

Background data

Mobius: Notes

2020-10-25T12:06:29Z

Notes

Mobius: Outcome

2020-10-25T12:01:53Z

Outcome

Mobius: Walkthrough

2020-10-25T11:54:15Z

Walkthrough

Mobius: Background

2020-10-25T11:11:54Z

Background

Mobius: Notable ships present

2020-10-22T17:08:43Z

Notable ships present

Nyctaeus at 16:01, 22 October 2020

2020-10-22T16:01:09Z

@@ Line 3: / Line 3: @@
 {{Mission|next=More than a Prophecy|previous=Possente Ftha, Immenso Ftha|campaign=Series Resurrecta Campaigns Walkthrough}}
-'''[[Shadows of the Great War]] - [[The Spirit of Ptah]] Mission 4'''
+'''[[Shadows of the Great War]] - [[The Spirit of Ptah]] Mission 4: Mask of a Fanatic'''
 '''Player squadron:''' [[Series Resurrecta Squadrons#223rd Moonbears|223rd Moonbears]] (transition to [[Series Resurrecta Squadrons#26th Yellow Lancers|26th Yellow Lancers]])

← Older revision		Revision as of 10:55, 30 December 2020
Line 6:		Line 6:

	'''Player squadron:''' [[Series Resurrecta Squadrons#223rd Moonbears\|223rd Moonbears]] (transition to [[Series Resurrecta Squadrons#26th Yellow Lancers\|26th Yellow Lancers]])		'''Player squadron:''' [[Series Resurrecta Squadrons#223rd Moonbears\|223rd Moonbears]] (transition to [[Series Resurrecta Squadrons#26th Yellow Lancers\|26th Yellow Lancers]])
		+
		+	'''System:''' [[Alpha Centauri]]

	'''Description:''' The Hikuptah has left Vasuda for Alpha Centauri, which is disputed. A former pilot from the GTD Ixion is deployed on a scout fighter, with two PVI special agents on board, to stage a defection and gain vital information...		'''Description:''' The Hikuptah has left Vasuda for Alpha Centauri, which is disputed. A former pilot from the GTD Ixion is deployed on a scout fighter, with two PVI special agents on board, to stage a defection and gain vital information...

@@ Line 23: / Line 23: @@
 Our designation will be ''Pi 1''. The mission objectives are rather straightforward, but please note that the mission may be long and while it doesn't involve much fighting, it does however require concentration and a good idea of what to do. After the cutscene, we'll find ourselves in [[Alpha Centauri]], and many [[Hammer of Light]] units of all kinds will be around, guarding the node connecting said system to [[Vasuda]]. The PVI agents Aidha and Rhadames will take care of the intel part, and while it may be a good idea to read the messages to monitor progress on the interaction with HoL fanatics, we have to be quick and scan as many ships as possible. Our scanning range has increased to over 700 meters, yet the scans will take quite some time to complete. Let's start with the [[Series Resurrecta Ship Database#PVC Anedjib|PVC ''Anedjib'']], then move to the remaining ships, including the [[Series Resurrecta Ship Database#HLD Prophecy|HLD ''Prophecy'']]. The [[Typhon]] will require its subsystems to be scanned, and due to the modifications of our scanning systems, each scan will be way slower than usual. We should be able to perform all indicated scans before the jump to the next stage of the mission, which will be automatic as any other warpout in this operation. The second stage of this intel operation is primarily focused on dialogue, with scanning being a side task. A long discussion will take place between the PVI agents onboard our fighter and the CO of the [[Series Resurrecta Ship Database#HLCv Hutyemhat|''Hutyemhat'']], a [[PVCv Sobek|Sobek prototype]]. We'll have plenty of time to scan the corvette, as well as the prototype [[PVF Ka|Ka]] fighters in ''Taurus'' wing. After the message exchanges, we'll be headed to a third sector of the system.
-The previous stages were a cakewalk compared to the third. We'll find ourselves in front of a [[Series Resurrecta Ship Database#Ifrit Research Structure|large structure]] built around a [[Demon]] destroyer, the [[Series Resurrecta Ship Database#SD Ifrit|SD ''Ifrit'']], as well as numerous HoL ships and fighters. We'll also see ten [[SB Nahema|Nahema]] bombers, yet more proof that the HoL have had access to more [[Shivan]] technology than previously thought. Our job is to scan all ships marked in the escort list, and that includes the main subsystems on the ''Ifrit'', as well as the Nahema bombers. Please note, however, that the presence of so many HoL ships in a constrained area like the research structure will result in their sensors showing better performances than before - in fact, you'll get a warning for approaching any of the HoL ships. At this point, randomization will determine your fate: the number of warnings you can get before the mission failes ranges between two and three, so you have to be cautious; don't worry, however, as all scans can be easily performed without getting a single warning. The mission will also fail if we don't perform all indicated scans after a certain amount of time, so be sure to maintain a constant pace and rely on the increase range of scanning to optimize your resources. At some point, a warship we'll soon learn to love and hate, the [[Series Resurrecta Ship Database#HLD Hedju Hor|HLD ''Hedju Hor'']], will jump in and deploy [[Scarab]] support ships to retrieve five Nahema bombers. We'll have to scan three of the [[PVD Atum|Atum]'s subsystems, but don't scan a fourth subsystem or the mission will fail. The retrieval operation is rather slow, so we should be able to perform these scans before the ''Hedju Hor'' warps out. Soon afterwards, the [[Series Resurrecta Ship Database#HLD Hikuptah|HLD ''Hikuptah'']] itself will enter the area and follow a similar pattern; that's where things get serious. We ''must'' scan all of the main subsystems on this warship before it completes its retrieval operation, and it may take minutes to do it. The destroyer's large and due to the distances involved, it's a good idea to scan the subsystems progressively without hopping from one side of the flagship to the other. Make sure to scan its engines all at once, for example, as they're grouped together. Its communication and navigation subsystems are also very close to each other, so you'd rather scan them altogether.
+The previous stages were a cakewalk compared to the third. We'll find ourselves in front of a [[Series Resurrecta Ship Database#Ifrit Research Structure|large structure]] built around a [[Demon]] destroyer, the [[Series Resurrecta Ship Database#SD Ifrit|SD ''Ifrit'']], as well as numerous HoL ships and fighters. We'll also see ten [[SB Nahema|Nahema]] bombers, yet more proof that the HoL have had access to more [[Shivan]] technology than previously thought. Our job is to scan all ships marked in the escort list, and that includes the main subsystems on the ''Ifrit'', as well as the Nahema bombers. Please note, however, that the presence of so many HoL ships in a constrained area like the research structure will result in their sensors showing better performances than before - in fact, you'll get a warning for approaching any of the HoL ships. At this point, randomization will determine your fate: the number of warnings you can get before the mission failes ranges between two and three, so you have to be cautious; don't worry, however, as all scans can be easily performed without getting a single warning. The mission will also fail if we don't perform all indicated scans after a certain amount of time, so be sure to maintain a constant pace and rely on the increase range of scanning to optimize your resources. At some point, a warship we'll soon learn to love and hate, the [[Series Resurrecta Ship Database#HLD Hedju Hor|HLD ''Hedju Hor'']], will jump in and deploy [[Scarab]] support ships to retrieve five Nahema bombers. We'll have to scan three of the [[PVD Atum|Atum]]'s subsystems, but don't scan a fourth subsystem or the mission will fail. The retrieval operation is rather slow, so we should be able to perform these scans before the ''Hedju Hor'' warps out. Soon afterwards, the [[Series Resurrecta Ship Database#HLD Hikuptah|HLD ''Hikuptah'']] itself will enter the area and follow a similar pattern; that's where things get serious. We ''must'' scan all of the main subsystems on this warship before it completes its retrieval operation, and it may take minutes to do it. The destroyer's large and due to the distances involved, it's a good idea to scan the subsystems progressively without hopping from one side of the flagship to the other. Make sure to scan its engines all at once, for example, as they're grouped together. Its communication and navigation subsystems are also very close to each other, so you'd rather scan them altogether.
 At this point we may believe we can pull back to Vasuda, but it won't be the case. The HoL flagship will interact with the ''Ifrit'' and all enemy ships in the area will withdraw. Due to the threat posed by the reactivation of a Shivan destroyer right in the middle of Vasudan controlled space, Rhadames will send a distress call to all Allied warships which can hear it, and two cruisers, the [[Series Resurrecta Ship Database#GTC Arusha|GTC ''Arusha'']] and the [[Series Resurrecta Ship Database#PVC Dedumose|PVC ''Dedumose'']], will jump in with some friendly wings to eliminate this threat. The ''Hutyemhat'' and its Ka escort fighters will jump in to interfere, but they will soon fall to prolonged barrage. Two Shivan cruisers, one [[Cain]] and a [[Lilith]], will emerge from subspace, awakened by the call of the ''Ifrit'', but they will also pose no critical threat to Allied forces. If things go as planned, the area will be cleared in minutes and the ''Ifrit'' itself will fall. Only at this point we'll be able to pull back to Vasuda, but there's one more obstacle to our return on the [[Series Resurrecta Ship Database#PVD Hedetet|PVD ''Hedetet'']]: as we approach the jump node, we'll notice a [[PVF Seshat|Seshat]] scout fighter moving towards the node itself, and said fighter would match our own in configuration. It's precisely what you think: the HoL are now attempting to send an impostor as a last resort to disrupt your scans of strategic assets. You may ignore the fighter, or you may destroy it - as long as you don't get too close to the various HoL wings that will jump in, you'll be fine. It's recommended to head straight to the node and complete the mission, however.

@@ Line 15: / Line 15: @@
 ----
 ==Background==
 The [[Series Resurrecta Ship Database#HLD Hikuptah|HLD ''Hikuptah'']], the [[Hammer of Light]] flagship that appeared from nowhere and eliminated the [[Series Resurrecta Ship Database#GTD Ixion|GTD ''Ixion'']] using powerful reverse-engineered [[beam weapon|beam weapons]] of [[Shivan]] origin, has eluded detection since that engagement and must be countered. The Alliance realizes that a pure engagement with the vessel, which is suspected to have set a course to [[Alpha Centauri]], would result in bloodshed, and relies on a side plan to gather vital data on the destroyer's specs and react according to said data. Despite the obvious advantage in term of firepower, the ''Hikuptah'' also plays a delicate political role, and may induce further defections within the [[PVE]]. [[Famous persons#Supreme Admiral Khu|Supreme Admiral Khu]] decides that experienced and skilled Terran pilots, all but impervious to HoL influence, may perform a task that would otherwise put any Vasudan pilot, no matter how loyal to the PVE, in an ambiguous situation.

@@ Line 53: / Line 53: @@
 ==Notes==
-''To be filled in later.''
+The [[Series Resurrecta Ship Database#HLCv Hutyemhat|HLCv ''Hutyemhat'']] was initially supposed to be an [[GVSC Imhotep|Imhotep]] science vessel. However, due to the prominence of its CO within the [[Hammer of Light]], as well as the ship's involvement in an engagement later on in the mission, it was ultimately proposed to introduce the [[Sobek]] prototype [[PVCv Sobek|Renenutet]].
 [[Category: Series Resurrecta]]

@@ Line 50: / Line 50: @@
 ==Outcome==
-''To be filled in later.''
+The plans to obtain vital data on the [[Series Resurrecta Ship Database#HLD Hikuptah|''Hikuptah'']] by relying on top of the notch PVI agents as well as a skilled Terran pilot were successful. Preliminary analysis of the scans doesn't show any major flaws in the ''Hikuptah'' designs, meaning that the Alliance will have to work hard on finding a strategy to stop the vessel. It has also become clear that the [[Hammer of Light]] has had access to many [[Shivan]] assets including the previously unencountered [[Nahema]] bomber, which gave a boost to the [[Sekhmet]] design, and the root for the [[PVF Ka|Ka]] fighter, which is also based on Shivan technology. There are many worrying implications of this discovery: one is purely strategical and tactical, as it proves how technologically advanced the enemy is; the second implication is that the HoL benefits from the huge support of corrupted members within the [[Vasudans#Culture|Parliament]], as none of these achievements and coverups would be possible without major help from influential politicians. Yet still, something has to be done to bring back peace to Allied space.
 ==Notes==

@@ Line 18: / Line 18: @@
 ==Walkthrough==
-''To be filled in later.''
+Our designation will be ''Pi 1''. The mission objectives are rather straightforward, but please note that the mission may be long and while it doesn't involve much fighting, it does however require concentration and a good idea of what to do. After the cutscene, we'll find ourselves in [[Alpha Centauri]], and many [[Hammer of Light]] units of all kinds will be around, guarding the node connecting said system to [[Vasuda]]. The PVI agents Aidha and Rhadames will take care of the intel part, and while it may be a good idea to read the messages to monitor progress on the interaction with HoL fanatics, we have to be quick and scan as many ships as possible. Our scanning range has increased to over 700 meters, yet the scans will take quite some time to complete. Let's start with the [[Series Resurrecta Ship Database#PVC Anedjib|PVC ''Anedjib'']], then move to the remaining ships, including the [[Series Resurrecta Ship Database#HLD Prophecy|HLD ''Prophecy'']]. The [[Typhon]] will require its subsystems to be scanned, and due to the modifications of our scanning systems, each scan will be way slower than usual. We should be able to perform all indicated scans before the jump to the next stage of the mission, which will be automatic as any other warpout in this operation. The second stage of this intel operation is primarily focused on dialogue, with scanning being a side task. A long discussion will take place between the PVI agents onboard our fighter and the CO of the [[Series Resurrecta Ship Database#HLCv Hutyemhat|''Hutyemhat'']], a [[PVCv Sobek|Sobek prototype]]. We'll have plenty of time to scan the corvette, as well as the prototype [[PVF Ka|Ka]] fighters in ''Taurus'' wing. After the message exchanges, we'll be headed to a third sector of the system.
 ==Notable ships present==

← Older revision		Revision as of 17:08, 22 October 2020
Line 18:		Line 18:

	==Walkthrough==		==Walkthrough==
		+	''To be filled in later.''
		+
		+	==Notable ships present==
		+	*Alliance
		+	**[[Series Resurrecta Ship Database#GTC Arusha\|GTC ''Arusha'']]
		+	**[[Series Resurrecta Ship Database#PVC Dedumose\|PVC ''Dedumose'']]
		+	*Hammer of Light
		+	**[[Series Resurrecta Ship Database#HLFr Khendjer\|HLFr ''Khendjer'']]
		+	**[[Series Resurrecta Ship Database#HLFr Nefaarud\|HLFr ''Nefaarud'']]
		+	**[[Series Resurrecta Ship Database#HLFr Osorkon\|HLFr ''Osorkon'']]
		+	**[[Series Resurrecta Ship Database#HLC Anedjib\|HLC ''Anedjib'']]
		+	**[[Series Resurrecta Ship Database#HLC Baenre\|HLC ''Baenre'']]
		+	**[[Series Resurrecta Ship Database#HLC Bensenu\|HLC ''Bensenu'']]
		+	**[[Series Resurrecta Ship Database#HLC Sobekhotep\|HLC ''Sobekhotep'']]
		+	**[[Series Resurrecta Ship Database#HLSC Merdjefar\|HLSC ''Merdjefar'']]
		+	**[[Series Resurrecta Ship Database#HLSC Nerikare\|HLSC ''Nerikare'']]
		+	**[[Series Resurrecta Ship Database#HLSC Setnakhte\|HLSC ''Setnakhte'']]
		+	**[[Series Resurrecta Ship Database#HLCv Hutyemhat\|HLCv ''Hutyemhat'']] (destroyed)
		+	**[[Series Resurrecta Ship Database#HLD Hedju Hor\|HLD ''Hedju Hor'']]
		+	**[[Series Resurrecta Ship Database#HLD Hikuptah\|HLD ''Hikuptah'']]
		+	**[[Series Resurrecta Ship Database#HLD Prophecy\|HLD ''Prophecy'']]
		+	**[[Series Resurrecta Ship Database#Ifrit Research Structure\|''Ifrit Research Structure'']] (destroyed)
		+	*Shivans
		+	**[[Series Resurrecta Ship Database#SC Blobhra\|SC ''Blobhra'']] (destroyed)
		+	**[[Series Resurrecta Ship Database#SC Gargantua\|SC ''Gargantua'']] (destroyed)
		+	**[[Series Resurrecta Ship Database#SD Ifrit\|SD ''Ifrit'']] (destroyed)
		+
		+	==Outcome==
	''To be filled in later.''		''To be filled in later.''

← Older revision		Revision as of 16:01, 22 October 2020
Line 1:		Line 1:
		+	{{SRArticle}}
		+
	{{Mission\|next=More than a Prophecy\|previous=Possente Ftha, Immenso Ftha\|campaign=Series Resurrecta Campaigns Walkthrough}}		{{Mission\|next=More than a Prophecy\|previous=Possente Ftha, Immenso Ftha\|campaign=Series Resurrecta Campaigns Walkthrough}}