Hacking Area - Revision history

Ian: See Also HoloMask State and Hacker/Hackable status, Cautious Movement, fixed HoloMask links.

2025-10-31T11:23:40Z

See Also HoloMask State and Hacker/Hackable status, Cautious Movement, fixed HoloMask links.

Ian: PDF N5.2 update.

2025-10-22T10:24:26Z

PDF N5.2 update.

Ian at 15:40, 25 April 2025

2025-04-25T15:40:41Z

Ian at 15:28, 25 April 2025

2025-04-25T15:28:26Z

Ian at 10:17, 23 April 2025

2025-04-23T10:17:41Z

Ian at 10:17, 23 April 2025

2025-04-23T10:17:06Z

Ian: N5 first version.

2025-03-27T12:05:38Z

N5 first version.

Show changes

Ian: PDF 2.1

2023-08-15T15:42:10Z

PDF 2.1

Ian: PDF 2.1

2023-08-15T15:36:14Z

PDF 2.1

Ian at 11:22, 21 December 2022

2022-12-21T11:22:11Z

@@ Line 13: / Line 13: @@
-==[[HoloMask]] and Hacking Area==
+==[[HoloMask State | HoloMask]] and Hacking Area==
 When using an [[Enemy]] [[Repeater]] to include an Enemy Trooper in the Hacking Area, any [[ARO]] or [[Hacking Program]] against a Trooper who does not have the [[Hacker]] Special Skill on their real [[Unit Profile]] will fail its Requirements in the [[Resolution]] step of the Order, and instead an [[Idle]] will be performed. This will reveal that the Enemy Trooper is not a Hacker.
-==[[HoloMask]] and Repeater==
+==[[HoloMask State | HoloMask]] and Repeater==
 Similarly, when using an [[Enemy]] Trooper’s [[Repeater]], if that Trooper is in [[HoloMask State]] and does not have a Repeater on their real [[Unit Profile]] then any [[ARO]] or [[Hacking Program]] using their fake Repeater will fail its Requirements in the [[Resolution]] step of the Order, and instead an [[Idle]] will be performed. This will reveal that the Enemy Trooper does not have a Repeater.

@@ Line 30: / Line 30: @@
 {{greybox-start | Example of Hacking Area and AROs Through Repeaters }}
 {{image | name=n5/eng-hacking-area-example-aros.jpg | style=fullborder }}
@@ Line 40: / Line 36: @@
 During his Active Turn, a Hacker decides to declare Idle as the first Basic Short Skill of the Order. As shown in the picture, he is outside his enemies' LoF and ZoC, but since he is a Hacker, he can use the Deployable Repeater and a Trooper with the Repeater piece of Equipment to increase his Hacking Area, allowing him to act from his current position.
-Therefore, since the Hacker is within the Hacking Area of the Enemy Hacker, the enemy declares his ARO: Oblivion.
+{{update | PDF 5.2, October 2025}}
-As the Enemy Heavy Infantry is in the Active Trooper's Hacking Area, they can declare an ARO, choosing to declare a Reset.
+{{erratahighlight}}The Enemy Heavy Infantry (HI) cannot declare an ARO as the Active Hacker is outside their LoF and ZoC.{{erratahighlight-end}}
 The second Skill of the Hacker is Carbonite, dividing his B2 between the Enemy Heavy Infantry and the enemy Hacker.
 The following Face to Face Rolls occur:
@@ Line 79: / Line 86: @@
 [[Category: Hacking]]

@@ Line 2: / Line 2: @@
-This term refers to the Area of Effect of [[Hacking Program]]s. In Infinity a [[Hacker]]’s Hacking Area matches their [[Zone of Control]], and the Zone of Control of [[Repeaters]] and [[Deployable Repeaters]] of either the Player or their Allies.
+This term refers to the Area of Effect of [[Hacking Program]]s. In Infinity a [[Hacker]]’s Hacking Area matches their [[Zone of Control]], and the Zone of Control of [[Repeater]]s and [[Deployable Repeater]]s of either the Player or their Allies.
 In addition, if a Hacker is within the Zone of Control of an [[Enemy]] Repeater or Deployable Repeater, their Hacking Area includes all Enemy Troopers on the game table. However, if the Enemy Trooper is not a Hacker, any [[ARO]] or [[Hacking Program]] using the Enemy Repeater will fail its Requirements, and instead an [[Idle]] will be performed.
@@ Line 10: / Line 10: @@
 Enemies entering or acting inside the Hacking Area of a [[Hacker]] while remaining outside that Hacker’s [[LoF]] and [[ZoC]] can be reacted to.
-In the ARO Check steps of the [[Order Expenditure Sequence]], players can check if the Active Trooper is inside any Reactive Troopers’ Hacking Areas. Measurements must always be made from the Active Trooper, checking a maximum of 8 inches from any point along their path, and from the Active Trooper’s [[Repeaters]]. If the measurements show that the Active Trooper is within the Hacking Area of the Reactive Trooper, they can declare an ARO.
+In the ARO Check steps of the [[Order Expenditure Sequence]], players can check if the Active Trooper is inside any Reactive Troopers’ Hacking Areas. Measurements must always be made from the Active Trooper, checking a maximum of 8 inches from any point along their path, and from the Active Trooper’s [[Repeater]]s. If the measurements show that the Active Trooper is within the Hacking Area of the Reactive Trooper, they can declare an ARO.

@@ Line 14: / Line 14: @@
 ==[[HoloMask]] and Hacking Area==
-When using an [[Enemy]] [[Repeater]] to include an Enemy Trooper in the Hacking Area, any [[ARO]] or [[Hacking Program]] against a Trooper who does not have the [[Hacker]] Special Skill on their real [[Unit Profile]] will fail its Requirements in the [[Resolution step]] of the Order, and instead an [[Idle]] will be performed. This will reveal that the Enemy Trooper is not a Hacker.
+When using an [[Enemy]] [[Repeater]] to include an Enemy Trooper in the Hacking Area, any [[ARO]] or [[Hacking Program]] against a Trooper who does not have the [[Hacker]] Special Skill on their real [[Unit Profile]] will fail its Requirements in the [[Resolution]] step of the Order, and instead an [[Idle]] will be performed. This will reveal that the Enemy Trooper is not a Hacker.
 ==[[HoloMask]] and Repeater==
-Similarly, when using an [[Enemy]] Trooper’s [[Repeater]], if that Trooper is in [[HoloMask State]] and does not have a Repeater on their real [[Unit Profile]] then any [[ARO]] or [[Hacking Program]] using their fake Repeater will fail its Requirements in the [[Resolution step]] of the Order, and instead an [[Idle]] will be performed. This will reveal that the Enemy Trooper does not have a Repeater.
+Similarly, when using an [[Enemy]] Trooper’s [[Repeater]], if that Trooper is in [[HoloMask State]] and does not have a Repeater on their real [[Unit Profile]] then any [[ARO]] or [[Hacking Program]] using their fake Repeater will fail its Requirements in the [[Resolution]] step of the Order, and instead an [[Idle]] will be performed. This will reveal that the Enemy Trooper does not have a Repeater.

@@ Line 8: / Line 8: @@
 ==Hacking Area in [[ARO]]==
-Enemies entering or acting inside the Hacking Area of a [[Hacker]] while remaining outside that Hacker’s [[LoF] and [[ZoC]] can be reacted to.
+Enemies entering or acting inside the Hacking Area of a [[Hacker]] while remaining outside that Hacker’s [[LoF]] and [[ZoC]] can be reacted to.
 In the ARO Check steps of the [[Order Expenditure Sequence]], players can check if the Active Trooper is inside any Reactive Troopers’ Hacking Areas. Measurements must always be made from the Active Trooper, checking a maximum of 8 inches from any point along their path, and from the Active Trooper’s [[Repeaters]]. If the measurements show that the Active Trooper is within the Hacking Area of the Reactive Trooper, they can declare an ARO.

@@ Line 2: / Line 2: @@
-This term refers to the Area of Effect of Hacking Programs. In Infinity a [[Hacker]]’s Hacking Area matches their [[Zone of Control]], and the Zone of Control of [[Repeaters]] and [[Deployable Repeaters]] of either the Player or their Allies.
+This term refers to the Area of Effect of [[Hacking Program]]s. In Infinity a [[Hacker]]’s Hacking Area matches their [[Zone of Control]], and the Zone of Control of [[Repeaters]] and [[Deployable Repeaters]] of either the Player or their Allies.
-In addition, if a Hacker is within the Zone of Control of an Enemy Repeater or Deployable Repeater, their Hacking Area includes all Enemy Troopers on the game table. However, if the Enemy Trooper is not a Hacker, any [[ARO]] or [[Hacking Program]] using the Enemy Repeater will fail its Requirements, and instead an [[Idle]] will be performed.
+In addition, if a Hacker is within the Zone of Control of an [[Enemy]] Repeater or Deployable Repeater, their Hacking Area includes all Enemy Troopers on the game table. However, if the Enemy Trooper is not a Hacker, any [[ARO]] or [[Hacking Program]] using the Enemy Repeater will fail its Requirements, and instead an [[Idle]] will be performed.
-==Hacking Area in ARO==
+==Hacking Area in [[ARO]]==
-Enemies entering or acting inside the Hacking Area of a Hacker while remaining outside that Hacker’s [[LoF] and ZoC can be reacted to.
+Enemies entering or acting inside the Hacking Area of a [[Hacker]] while remaining outside that Hacker’s [[LoF] and [[ZoC]] can be reacted to.
-In the ARO Check steps of the [[Order Expenditure Sequence]], players can check if the Active Trooper is inside any Reactive Troopers’ Hacking Areas. Measurements must always be made from the Active Trooper, checking a maximum of 8 inches from any point along their path, and from the Active Trooper’s Repeaters. If the measurements show that the Active Trooper is within the Hacking Area of the Reactive Trooper, they can declare an ARO.
+In the ARO Check steps of the [[Order Expenditure Sequence]], players can check if the Active Trooper is inside any Reactive Troopers’ Hacking Areas. Measurements must always be made from the Active Trooper, checking a maximum of 8 inches from any point along their path, and from the Active Trooper’s [[Repeaters]]. If the measurements show that the Active Trooper is within the Hacking Area of the Reactive Trooper, they can declare an ARO.
 ==[[HoloMask]] and Hacking Area==
-When using an Enemy Repeater to include an Enemy Trooper in the Hacking Area, any ARO or Hacking Program against a Trooper who does not have the Hacker Special Skill on their real Unit Profile will fail its Requirements in the Resolution step of the Order, and instead an Idle will be performed. This will reveal that the Enemy Trooper is not a Hacker.
+When using an [[Enemy]] [[Repeater]] to include an Enemy Trooper in the Hacking Area, any [[ARO]] or [[Hacking Program]] against a Trooper who does not have the [[Hacker]] Special Skill on their real [[Unit Profile]] will fail its Requirements in the [[Resolution step]] of the Order, and instead an [[Idle]] will be performed. This will reveal that the Enemy Trooper is not a Hacker.
-==HoloMask and Repeater==
+==[[HoloMask]] and Repeater==
-Similarly, when using an Enemy Trooper’s Repeater, if that Trooper is in HoloMask State and does not have a Repeater on their real Unit Profile then any ARO or Hacking Program using their fake Repeater will fail its Requirements in the Resolution step of the Order, and instead an Idle will be performed. This will reveal that the Enemy Trooper does not have a Repeater.
+Similarly, when using an [[Enemy]] Trooper’s [[Repeater]], if that Trooper is in [[HoloMask State]] and does not have a Repeater on their real [[Unit Profile]] then any [[ARO]] or [[Hacking Program]] using their fake Repeater will fail its Requirements in the [[Resolution step]] of the Order, and instead an [[Idle]] will be performed. This will reveal that the Enemy Trooper does not have a Repeater.
@@ Line 25: / Line 25: @@
 {{image | name=n5/eng-hacking-area-example.jpg | style=fullborder }}
-The Hacker may use their Hacking Programs in the area that includes the Zone of Control of the Repeater, the Deployable Repeater and their own Zone of Control.
+The [[Hacker]] may use their [[Hacking Program]]s in the area that includes the [[Zone of Control]] of the [[Repeater]], the [[Deployable Repeater]] and their own [[Zone of Control]].
 {{greybox-end}}
@@ Line 64: / Line 64: @@
 {{greybox-start | Example of Camouflaged State and ARO Through a Repeater }}
-This time, the Hacker is in Camouflaged State and declares Idle.
+This time, the [[Hacker]] is in [[Camouflaged State]] and declares [[Idle]].
-As the Camouflaged Marker is inside the Enemy Hacker's Hacking Area, the Enemy Hacker can delay their ARO in case the Camouflaged Marker is a Hacker.
+As the Camouflaged Marker is inside the [[Enemy]] Hacker's [[Hacking Area]], the Enemy Hacker can delay their [[ARO]] in case the Camouflaged Marker is a Hacker.
 The Enemy Hacker may declare an ARO only if the Camouflaged Marker reveals themselves with the second Short Skill of the Order.

@@ Line 51: / Line 51: @@
 {{image | name=eng-hacking-area-aro-1024.jpg | style=512border }}
-{{update | 1.1.1, Dec 2021}}
+{{update | PDF 2.1, July 2023}}
-{{erratahighlight}}In this example, [[Stealth]] is not being used.{{erratahighlight-end}}
+{{erratahighlight}}For the sake of simplicity, in this example, the [[Stealth]] Special Skill is not being used.{{erratahighlight-end}}
 During his Active Turn, the Shrouded Hacker decides to declare Idle as the first Short Skill of the Order. As shown in the picture, he is outside his enemies LoF {{erratahighlight}}and ZoC{{erratahighlight-end}}, but since he is a Hacker, he can use the Deployable Repeater, and the M-Drone Trooper (who carries the Repeater piece of Equipment), to increase his Hacking Area, allowing him to act from his current position.
-{{erratahighlight}}As the Shrouded Hacker is inside the Orc Hacker’s Hacking Area, the Orc Hacker declares an ARO.{{erratahighlight-end}}
+{{erratahighlight}}Therefore, since the Shrouded Hacker is within the Hacking Area of the Orc Trooper Hacker, this declares his ARO: Oblivion.{{erratahighlight-end}}
 {{erratahighlight}}The Orc Hacker declares Oblivion.{{erratahighlight-end}}
@@ Line 62: / Line 62: @@
 The second Skill of the Shrouded Hacker is Carbonite, dividing his B2 between the Knight of Justice and the Orc Hacker.
-{{erratahighlight}}The Knight of Justice has now been targeted by a Hacking Program, given she an ARO, and she declare Reset.{{erratahighlight-end}}
+{{erratahighlight}}As the Knight of Justice has been targeted by a Hacking Program, she can declare ARO, choosing to declare a Reset.{{erratahighlight-end}}
 {{update-end}}

@@ Line 16: / Line 16: @@
-==Hacking Area and AROs==
+==Hacking Area in ARO==
-{{update | 1.3, Nov 2022}}
+{{update | PDF 2.1, July 2023}}
-Enemies entering or acting inside the Hacking Area of a Hacker while remaining outside that Hacker’s [[LoF]] and ZoC can be reacted to with Hacking Programs or with Reset.
+Enemies entering or acting inside the Hacking Area of a Hacker while remaining outside that Hacker’s [[LoF]] and ZoC can be reacted to.
 {{erratahighblock}}
-In the ARO Check steps of the [[Order Expenditure Sequence]], players can check if the Active Trooper is inside any Reactive Troopers' Hacking Areas. Measurements must always be made from the Active Trooper, checking a maximum of 8 inches from any point along their path, and from the Active Trooper’s Repeaters. If the measurements show that the Active Trooper is within the Hacking Area of the Reactive Trooper, they can declare a Hacking Program or Reset ARO, as mentioned above.
+In the ARO Check steps of the [[Order Expenditure Sequence]], players can check if the Active Trooper is inside any Reactive Troopers' Hacking Areas. Measurements must always be made from the Active Trooper, checking a maximum of 8 inches from any point along their path, and from the Active Trooper’s Repeaters. If the measurements show that the Active Trooper is within the Hacking Area of the Reactive Trooper, they can declare an ARO.
 ==[[HoloMask]] and Hacking Area==
@@ Line 33: / Line 33: @@
 {{original | 1.2, Jan 2022}}
-Enemies entering or acting inside the Hacking Area of a Hacker while remaining outside that Hacker’s [[LoF]] and ZoC can be reacted to with Hacking Programs or with Reset.
+Enemies entering or acting inside the Hacking Area of a Hacker while remaining outside that Hacker’s [[LoF]] and ZoC can be reacted to {{originalhighlight}}with Hacking Programs or with Reset{{originalhighlight-end}}.
 {{originalhighblock}}Players can check the Hacking Area. Measurements must always be made from the [[Active Trooper]] and their Repeaters, checking a maximum of 8 inches from any point along their path. If the Active Trooper is within the Hacking Area of the Reactive Trooper, they can declare an ARO (See [[Order Expenditure Sequence]]).{{originalhighblock-end}}